On Mon, 22 Jul 2013 17:40:23 +0200, Stephan Beal <sgb...@googlemail.com>
wrote:
On Mon, Jul 22, 2013 at 5:34 PM, Stephan Beal <sgb...@googlemail.com>
wrote:
On Mon, Jul 22, 2013 at 4:47 PM, Jacek Cała <jacek.c...@gmail.com>
wrote:
- project create initializes internal repo ticket number with '1',
- project clone adds suffix '.1' to the repo ticket number,
Alternate suggestion: we simply print the SHAs in decimal form ;).
They're
not sequential but at least they're human-readable ;).
A lot of people who are _much_ brainier than i have determined that the
sequential numbering problem cannot be solved for DVCS systems, and i
tend
to trust their judgement/calculations. As soon as you give up a central
authority, sequential numbering becomes impossible to properly implement.
that issue has come up before and I believe you are right w.r.t. a
globally valid sequential numbering being impossible (and translating the
'topology' of checkins and repos/clones by something like 1.2.3 does not
seem to help much, either, although it sure is possible in principle).
still, I would _much_ prefer to be able to perform all local actions on a
repo using _locally_ unambiguous sequential numbering of all checkins
(just like `hg' has always been doing it: checkins are denoted by
something like 10:0cb3d1256b... where the `10' is the locally valid
incremental index of the checkin which can be used instead of the sha1
hash in all commands). one obvious example being inspection of diffs
between consecutive checkins.
I also have never heard that use of such sequential numbering has caused
confusion for hg users (as long as it is understood not to talk about
"checkin number 10" across different clones of the project repo).
for the wishlist: this would be 'nice to have'.
as would be a facility to get the complete timeline output without having
to guess/enter a sufficiently large number for the `-n' flag....
and of course `grep'.
j.
--
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
