On Thu, Jan 10, 2013 at 12:56 PM, j. van den hoff <veedeeh...@googlemail.com > wrote:
> I would find it useful if `fossil info' (or `stat', `timeline', or a new > command) would provide a means/option to show the total number of revisions > (by default or optional), more precisely, the number of "file commits" (as > it is called in `fossil help timeline) in the repo. the information should > be there in the database (or could be added?) and an additional line of > output in `fossil info' would then do the trick. (sure one could also write > a script analyszing `fossil timeline -ci ...' output to derive this > information but this is not desirable for large repos in my view.) > i'll sign up for adding that - i would be able to do this on Sunday. i would add it to the "status" command because we have that info in the /stat page already (and in "fossil json stat -full"). > ps: while I'm at it: adding the relative revision numbers to the output of > `fossil timeline -ci' _and_ making them acceptable as keys instead of the > SHA1 hashes in the relevant commands (notably `diff') would be very nice, > too, but probably require more substantial changes. The DVCS model means that _relative_ (sequential) revision numbers are rendered absolutely meaningless because multiple users can work offline in parallel (and their system clocks might not be properly synced, breaking time-based ordering). The sequential numbering problem is, in effect, impossible to solve in a DVCS. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
