On Wed, Sep 4, 2013 at 2:53 PM, Jan Nijtmans <[email protected]> wrote:
> (further deviating from the original subject)
> How about:
> fossil commit --close --branch commit-close
> Hm, that's what I just did ;-)
>
i rather liked that feature - i see now that you closed it.
And back to the topic, here's a real-world, but small, example of
data collected since yesterday:
Main fossil repo:
stephan@tiny:~/cvs/fossil/fossil$ f usage
CLI command usage history for this checkout:
Count Command
4 status
3 diff
3 usage
2 commit
1 update
i cleared the usage history several times during testing of the feature,
but that's what i've done since then.
libfossil repo:
stephan@tiny:~/cvs/fossil/libfossil$ f usage
CLI command usage history for this checkout:
Count Command
7 status
3 commit
3 extras
2 diff
1 add
1 clean <--- my first-ever 'fossil clean', i think
1 usage
so i'm clearly a status fanatic (it's aliased to "fst" on all my systems).
That is probably historical, me having come from CVS/SVN. Fossil later
added "changes", which is an abbreviated form of status. timeline isn't in
there because i've almost always got a browser tab open to the timeline of
the central copy of whatever i'm working on. i use it occasionally, though.
Thanks again to Ross for the idea. One of these days i'll integrate that
into libfossil's CLI API.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
