Yaroslav Halchenko wrote: > one issue I have discovered which seems to complicate such use case: > git-annex seems to not track the content to any degree assuming > that those data files are really immutable. Although it is not > common, our data files might change, and it seems there is no way in > annex to track multiple "blobs" for the same filename?
This is up to the key-value backend used for the file. The default backend is WORM (write once, read many). The unfinished SHA1 backed will include the checksum in the key, so will track content -- but I'm unsure yet how efficient it will be. http://git-annex.branchable.com/backends/ -- see shy jo
Description: Digital signature
_______________________________________________ vcs-home mailing list firstname.lastname@example.org http://lists.madduck.net/listinfo/vcs-home