On Thu, 10 Jan 2013 13:51:51 +0100, Stephan Beal <sgb...@googlemail.com>
wrote:
On Thu, Jan 10, 2013 at 1:35 PM, Stephan Beal <sgb...@googlemail.com>
wrote:
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").
Don't tell my boss this, but...
http://fossil-scm.org/index.html/info/acea7010b8
i added the output to "info" instead of "status" because that seemed to
be
the better place for it (status reports local change status).
I just tested it and I stumbled: the reported checkin count is
_approximately_ (order of magnitude...) correct
but does _not_ match the actual number of checkins (nor the number of file
checkins only).
e.g. for the fossil repo itself (as of today at e4ca677a6c), `fossil info'
reports
checkin-count: 4845
however, I do see a total (files+wiki+ticket) of 8799 checkins and
fossil time -t ci -n 11111|grep ^[0-9]|wc -l
yields 4009.
so what is `checkin-count' actually reporting??
what I currently would find most useful is to see the total number (8799
in the example), but maybe instead a more
detailed statistics (file ci: xxx; wiki ci: yyyy, bug ci: zzzz) is also of
interest.
thanks
j.
ps:
in the long run I would really like to have fossil report chronological
local revision numbers in the timeline (cumulative across files, wiki,
tickets)
in addition to the hashes (plus abilitity to use themas "alias" in all
commands currently requesting specification of hashes). that would be at
least "nice to have" in order to facilitate interaction with fossil,
notably when using commands like `diff', `cat', etc.
[stephan@host:~/cvs/fossil/fossil]$ f info
project-name: Fossil
...
checkin-count: 4840
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
