package: git-annex version: 0.11 Currently, git-annex unlock will copy the raw bytes from its internal store, so that the file could be modified. However, some editing workflows don't actually modify the file, and just write out the new contents.
Consider the case of a workflow that writes the new version of the file to a tmp location, then does an atomic move to the old name. Since git-annex unlock copies the file, this means that the full file ends up being copied twice. Also, if the new version of the file is just a truncated version(consider a file going from 200Mbytes to 5 bytes), then the unlock copy is a waste of disk io. My suggestion in this case is to hard-link. The workflow I am thinking of modifying(wiki-like web frontend, with support for uploading of videos), already has a pre-commit hook, which would use git-annex unlock first, and a post-commit hook that then would commit the changes back. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
