On 3/12/2016 11:45 PM, Baruch Burstein wrote:
On Sat, Mar 12, 2016 at 2:27 AM, Ross Berteig <[email protected]> wrote:
On 3/11/2016 3:40 PM, Joe Mistachkin wrote:
....
I don't feel strongly about gone or not, but consistent would be
good. IIRC there was some resistance to the original version of this
change where it was totally gone, and the current state where fusefs
became a secondary command that fails was the result of that.
https://www.mail-archive.com/fossil-dev%40mailinglists.sqlite.org/msg00374.html
That email thread seems to imply a preference from drh in particular
(and others too) for keeping the fossil fusefs command but demoting it
to the help -a list when not configured. With a strong implication that
the current implementation of fossil json is thus wrong.
I've personally never used the fusefs support, but I do wonder if the
command shouldn't *always* be demoted to the help -a list. Is it really
the sort of command that is used every day by novice users?
Perhaps we should do that for fossil json now, and I think the same
argument about help -a applies. I'll poke at that, see what pokes back.
[snip]
* baruch_timeline_fixes
....
I thought I remembered some discussion, but my google-fu is failing
me today. The obvious test of just loading /timeline in fossil ui
and clicking older and newer worked. I didn't poke at it much more
than that.
https://www.mail-archive.com/fossil-dev%40mailinglists.sqlite.org/msg00419.html
Thanks for the pointer. I built and tested this again, and now that I
see what it is doing it all looks great. I'm merging it to trunk now.
--
Ross Berteig [email protected]
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-dev mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
