On 09/09/15 20:12, j. van den hoff wrote:
On Wed, 09 Sep 2015 20:19:04 +0200, Ron W <[email protected]> wrote:
On Wed, Sep 9, 2015 at 7:19 AM, Luca Ferrari <[email protected]>
wrote:
Some DVCS, like hg, use both an hash and a sequential number.
As I recall (been a few years since I last used hg), the numbers were
"relative" to the output of hg's equivalent to "timeline".
Assuming I am remembering correctly, if Fossil had this feature, you
could
do something like:
$ 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 1
uuid: 10a5af61c1fc25060ad428de9c82e3615b45f6c8 ...
The numbers, of course, could change after any sync or commit.
in a breach of promise to myself to never again argue in favour of
this functionality on the fossil mailing list (it came up a few times
over the last years):
having simple chronological checkin numbers as an alternative way of
specifying checkins _locally_ just the way hg has done for years
would be a *good* thing. simply because for most projects (all the
small ones out there) specifying chronological numbers is
shorter/easier than specifying (unique min 4-digits prefixes of) sha1
hashes. and the "chronologic property" itself is helpful in itself,
e.g in comparing 'current vs. previous' checkin. and until checkin
9999 its at least break even in terms of typing effort. the fact that
those chronological checkin numbers are a local property of each
clone/checkout rather than of the repo proper is beside the point in
my view: it is true but mostly irrelevant. I concede that there might
arise confusion if people are really not aware of the potential
ambiguity of those chronological numbers across different clones if
they start to argue about a certain checkin. but when interacting with
fossil it cannot have adverse effects afaiks. rather the opposite
Sounds to me like you need a GUI.
I need to get my backside into gear and finish this:
www.p-code.org/fcommit. But you could try it out, because it's very
convenient for doing what you describe.
It's got a history dialog with links down the left. As you click on the
links a diff window updates with the changes for that checkin. If you
Ctrl and click on a link it will change colour to yellow. Ctrl-click on
another link and it will also change to yellow. Press control-d then
press ok to see a diff between the two checkins.
Some things are just more convenient with a GUI.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
