On Thu, Sep 10, 2015 at 9:17 AM, j. van den hoff <veedeeh...@googlemail.com>
wrote:
>
> well, I'm only talking about the ordinal numbers chronologically
> enumerating the timeline checkin(!) entries. this enumeration will not
> change as a consequence of rebuild, right? it might change after a sync
> against some remote repo if there are incoming checkins chronologically
> interleaved with my own, sure, but so what? the relative numbers would be
> just a (somewhat "volatile") convenience measure _locally_. and I agree
> with another recent post that this would primarily concern the CLI. what I
> mean: go ask some hg users when they last did use sha1 hashes for
> specifying checkins in their interaction with hg (which supports both the
> ordinals as well as the hashes for doing so) and how often the presence of
> those numbers confused communication with other developers in their
> project. I'm quite sure they _never_ specify sha1 hashes to denote checkins
> in any small to medium-sized project below 10^4 checkins (currently
> this still includes fossil itself). not so sure about the "communication"
> issue if users forget the potentially 'volatile' nature of the relative
> enumeration, but this just can't possibly be a big issue ...
For the project (a few years ago) I used Hg, yes, for my *local*
interaction with Hg, I did use the sequential numbers to save typing (or
copy/paste) the hashes.
When communicating with others, I used the hash.
In my earlier post, I had misremembered Hg's numbering. I had thought it
was in reverse order. But it is actually in commit order.
Personally, I would find some kind of relative specification more useful.
For example, if I could say "fossil gdiff --from cur-3" and get a diff
between the current check out and the revision 3 commits before the
revision the check out is from - along the same branch. If that would go
beyond the beginning of the branch, then continue back into the "parent"
branch from the branch point.
Revising my earlier example to more closely reflect this "relative"
concept:
$ fossil timeline -N -n 3
0 [d28be5063a] *CURRENT* Fix linker parameter file
-1 [10a5af61c1] Alt code for HS interface
-2 [5250e3796e] Increase speed threshold
$ fossil info -r cur-1
uuid: 10a5af61c1fc25060ad428de9c82e3615b45f6c8 ...
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
