unannex: Now skips files whose content is not present, rather than it being an error. This allows gradual conversion from one backend to another by running unannex followed by add in each repository.

This commit is contained in:
Joey Hess 2011-01-08 15:14:41 -04:00
parent 82fe151f87
commit 32b0e10390
4 changed files with 33 additions and 6 deletions

View file

@ -277,6 +277,19 @@ add something like this to `.gitattributes`:
* annex.backend=SHA1
## migrating between backends
Perhaps you had been using the WORM backend, but now have configured
git-annex to use SHA1 for new files. Your old files are still in WORM. How
to migrate that content? A quick and dirty way is to use the unannex
subcommand, which removes a file from git-annex's control, followed by
a re-add of the file, to put it in the new backend.
# git annex unannex my_cool_big_file
unannex my_cool_big_file ok
# git annex add my_cool_big_file
add my_cool_big_file (checksum ...) ok
## unused data
It's possible for data to accumulate in the annex that no files point to