> I'm a little concerned about accidental collisions, in the baz proposal:
> http://wiki.gnuarch.org/Win32FriendlyFormats
> The SHA checksums are postfixed with a number -1, -2, etc to allow for
> collisions that have different contents.
In the context of `git' you could not use numbers like that since there
is no central authority to allocate them.
One *could* use a probabilistically unique, user-selected id on the
other hand.
In Arch-speak, this would be like naming each blob with:
<sha1>,<size>,<id-tag>
If id-tags have internal structure that reflects their origin
(e.g., the way I stick "[EMAIL PROTECTED]" in mine), a blob-db
based system could filter out blobs whose id-tag statements
of their origin do not match where the data is coming from.
That would `git' pretty impregnable but at very high practical cost, I
think. It would complicate the politics of `git' a lot, making them
harder to think about. Perhaps that's something for `git 2.0' (if
such a thing is ever needed)?
-t
_______________________________________________
Gnu-arch-users mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-arch-users
GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
