Stephan Beal wrote:
>Correct, because fossil's only way of knowing the identity of a file is its
>name. If you take my name, everyone will think you're me.
>Nothing i can do about that. The SHA1 unique identifies the version of the
>content, but the name gives us a place under which to organize that.
I see the simplistic approach. On the other hand, if I decided to change my
name at some point, the authorities should be able to trace my current name to
my birth name, to figure out who I am, and my ‘criminal’ record should not
disappear!!!
Anyway, (as a future enhancement, perhaps) if FOSSIL knows in its trail of
changes from version A to version B that a file was renamed it should be able
to figure out and locate the correct file (by name) in the old version and do a
correct DIFF, while giving the “doesn’t exist” error if the file was not yet
introduced (by ADD or ADDR). And, obviously, FOSSIL does know, as it can be
seen from the UI (“Name change from ... to ...”).
Of course that would mean that to find what filename to compare it with, it
should do a walk-thru of all intermediate checkins from A to B, and not just
look at the two versions as two independent checkins (which I suspect is what
happens now) without regard to what happened in between (and I mean only in
relation to name changes, of course, not their contents).
Thanks.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
