coming back to the "limit reached" messages recently added to the
`timeline' output:

it sure is not a very big deal but I wonder whether somebody would explain
the rationale for these additions. personally, right now, I don't get it:

1.
the fact that `fossil timeline' by default does not (as most other RCSs)
display the full timeline but rather a very small fraction
should be known to everybody using `fossil' (there are really
substantially less easy to find bits of information in the help pages...)
so I find the 'line limit (20) reached' message completely redundant. I
_know_ that...

2.
now, if I type `fossil timeline -n 20' the system tells me (most of the
time, about from day 1 or 2 of the project...):
"entry limit (20) reached". yes, I know _that_ one, too, since I've just
typed it.

3.
if I type `fossil timeline -n 0' instead I get "end of timeline (nnn)".
guess what? I know it (except the nnn value which I don't need) already...

regarding this last message, of course I understand that there are the
cases where there are less than 20 lines in the log or less than the
specified number of entries and that this message allows to identify this.
so no. 3 might be reasonable but no. 1 and 2? and
regarding the 3. one, personally (yes, it has already been discussed w/o
success here, I know...) I still believe that providing an
additional chronological enumeration of the entries in addition to the
sha1 hashes would be useful and also solve this issue: if the timeline
display goes down to `0:[sha1]' I already see that the end is reached.
this of course also would make the other messages superfluous.

4.
a related thing: `-n N' restricts the display to N entries while the
"default" of this option is to display 20 lines. this is not really
consistent in my view. it would seem better to specify the default as a
certain number of entries, too (and thus drop the distinction between
messages no. 1 and 2 above)

otherwise I'm thankful for the recent changes to the timeline. both, the
fact that `-n' (finally...) now really limits the output to the
specified number of entries and `-W 0' enforces one line per checkin
output are really helpful.

j.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to