Thanks for the pointer Andy. (it should be .infoComment not .timelineComment)
This is for the Fossil Web UI.
How can I get it from the command prompt?
What I need is from the output of [fossil] timeline.
Thanks.
On Tuesday, April 15, 2014 10:30 AM, Andy Bradford
This is really a great tool!
To be even better, it would be nice to have some keystrokes to
navigate through the differences. Just to mimic tkdiff, I propose:
letter n - go to the following difference
letter p - go to the previous difference
Also, there is a bug to correct: if pressing save as
On Wed, Apr 16, 2014 at 12:49 PM, Ramon Ribó ram...@compassis.com wrote:
What is exactly Save as saving?
Richard recently added the ability to generate a standalone TCL script from
the diff which works like the diff -tk option, so that people can send
those scripts around.
If i'm not sorely
Oh. Got it. Thanks!
On Tue, Apr 15, 2014 at 3:29 PM, Richard Hipp d...@sqlite.org wrote:
On Tue, Apr 15, 2014 at 1:11 AM, Urmil Parikh urmilpar...@gmail.comwrote:
The artifact view of fossil is expected to show artifact content as text
(e.g.
We are seeing quite a few of these sync failures on busy repositories:
fossil commit cfgdat tests -m Added another drc test
Autosync: ssh://host/path/project.fossil
Round-trips: 1 Artifacts sent: 0 received: 0
Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT
m1 FROM
On Wed, Apr 16, 2014 at 6:01 PM, Matt Welland estifo...@gmail.com wrote:
Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT
m1 FROM time_fudge WHERE mid=objid) WHERE objid IN (SELECT mid FROM
time_fudge);}
Round-trips: 1 Artifacts sent: 0 received: 0
Pull finished
On Wed, Apr 16, 2014 at 9:14 AM, Stephan Beal sgb...@googlemail.com wrote:
On Wed, Apr 16, 2014 at 6:01 PM, Matt Welland estifo...@gmail.com wrote:
Error: Database error: database is locked: {UPDATE event SET
mtime=(SELECT m1 FROM time_fudge WHERE mid=objid) WHERE objid IN (SELECT
mid FROM
On Wed, Apr 16, 2014 at 6:22 PM, Matt Welland estifo...@gmail.com wrote:
then try the sync again and then report the fossil will fork message if
appropriate or follow though with the commit if the overlapping commit was
on a different branch.
Ah, right - i didn't think that through to the
On Wed, Apr 16, 2014 at 06:26:49PM +0200, Stephan Beal wrote:
Ah, right - i didn't think that through to the next step. That does indeed
sound like it would be an improvement. This weekend is a four-day one for
us in southern Germany (for Easter), so i'll see if i can tinker with this
if
On Wed, Apr 16, 2014 at 6:35 PM, Joerg Sonnenberger jo...@britannica.bec.de
wrote:
It would also be nice if clone didn't abort with removal of the
repository on such errors. pull/push should return an error etc.
There are a bunch of basic usability issues in this area. This is made
worse by
On Wed, Apr 16, 2014 at 11:35 AM, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
It would also be nice if clone didn't abort with removal of the
repository on such errors. pull/push should return an error etc.
There are a bunch of basic usability issues in this area. This is made
worse by
11 matches
Mail list logo
