Adam Heath wrote: > When using the SHA1 backend, it becomes possible to track changes to > files over time. A standard annex unlock, modify, git add/commit will > add a new object to the annex store, with an updated symlink at the > correct location. > > Over time, this could lead to a large number of files in the local > object store, and in any shared remotes. > > The SHA1 backend should store the raw byte data in a hashed layout, > using the same 2-char prefix that git normally uses, to solve this > problem.
I have thought about adding hashing. I think it's only needed on older filesystems though (probably not on ext4 or btrfs) so I am not sure.. BTW, any backend could be affected, if you have a lot of annexed files. The log files in .git-annex/ are the most likely initial pain point. I have 35000 in that one directory on mostly ext4 with no problem so far. -- see shy jo
signature.asc
Description: Digital signature
