Your message dated Fri, 18 Mar 2011 09:52:00 -0400
with message-id <[email protected]>
and subject line closing
has caused the Debian Bug report #606575,
regarding git-annex sha1 backend should be hashed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
606575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606575
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: git-annex
version: 0.11
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.
--- End Message ---
--- Begin Message ---
notfound 606575 0.20110317
thanks
Hashing was added in the last release but I forgot about this bug.
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
