On 12/11/16, Andy Goth wrote:
> http://core.tcl.tk/tcl/timeline?a=b40778af44=7054e2f2eb
Fixed.
>
> The marked check-in merges from trunk, but trunk is not visible on the
> timeline. In similar situations in the past I believe there were merge
> arrows coming from the
http://core.tcl.tk/tcl/timeline?a=b40778af44=7054e2f2eb
The marked check-in merges from trunk, but trunk is not visible on the
timeline. In similar situations in the past I believe there were merge
arrows coming from the bottom of the timeline, but in this instance
only the horizontal line is
On Sun, Jan 20, 2013 at 1:35 AM, Marc Simpson m...@0branch.com wrote:
It seems that commit [f76d912f1d] (which modified the base SQL used in
timeline queries) has introduced a bug into trunk: nothing is returned when
event types are specified as switches to `timeline'.
Fix here:
On Sun, Jan 20, 2013 at 4:29 PM, Richard Hipp d...@sqlite.org wrote:
On Sun, Jan 20, 2013 at 1:35 AM, Marc Simpson m...@0branch.com wrote:
It seems that commit [f76d912f1d] (which modified the base SQL used in
timeline queries) has introduced a bug into trunk: nothing is returned when
It seems that commit [f76d912f1d] (which modified the base SQL used in
timeline queries) has introduced a bug into trunk: nothing is returned when
event types are specified as switches to `timeline'.
Demonstration: here's the timeline for wiki pages in the main Fossil repo
output by build
On Wed, Jan 16, 2013 at 5:48 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
is this a bug or a feature? I do hope the former since it's really bad
behaviour when driving `fossil' with a script.
It's an as designed bug. The argument handling is based on the argument
count, and an empty
On Wed, 16 Jan 2013 18:28:24 +0100, Stephan Beal sgb...@googlemail.com
wrote:
On Wed, Jan 16, 2013 at 5:48 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
is this a bug or a feature? I do hope the former since it's really bad
behaviour when driving `fossil' with a script.
It's an as
On Wed, Jan 16, 2013 at 6:54 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
thanks for clarification. I understand that empty arguments can make sense
in some cases
(whether empty commits really do, we don't quite agree, obviously...) but
I nevertheless don't understand
what
We
On Wed, 16 Jan 2013 17:48:52 +0100, j. van den hoff
veedeeh...@googlemail.com wrote:
hi,
incidentally (when calling fossil from with a script constructing the
suitable call) I noted that
+fossil timeline ''+
(i.e. appending an empty string '' after `timeline') shows the
for completeness sake: did not hit 'reply all' the first time (thus
skipped replying to the list), so here it is.
On Wed, 16 Jan 2013 20:55:48 +0100, Eric e...@deptj.eu wrote:
On Wed, 16 Jan 2013 17:48:52 +0100, j. van den hoff
veedeeh...@googlemail.com wrote:
hi,
incidentally (when
10 matches
Mail list logo