Fossil uses unique prefixes of checksums as identifiers. What does it
do when a previously-unique prefix becomes ambiguous due to a new commit?
Also, what happens when an existing comment (or ticket or wiki page or
whatever) references a no-longer-unique prefix? Fossil can't rewrite
the old manifest without changing every checksum forward, so its only
hope is to change the display, but that leads to more problems.
It's quite likely this has already been discussed and resolved, but I
haven't been able to track down any emails or documentation on the matter.
I wish I could give you a test case, but the SHA1 function is thankfully
difficult to invert, even for prefixes. :^)
--
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
