mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

split the walkthrough and inline back together

Browse source
This commit is contained in:
Joey Hess 2011-02-27 12:45:48 -04:00
parent 9e49a71282
commit 98e246b49b
20 changed files with 386 additions and 420 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/walkthrough/migrating_data_to_a_new_backend.mdwn Normal file
View file

@ -0,0 +1,16 @@
Maybe you started out using the WORM backend, and have now configured
git-annex to use SHA1. But files you added to the annex before still
use the WORM backend. There is a simple command that can migrate that
data:
# git annex migrate my_cool_big_file
migrate my_cool_big_file (checksum...) ok
You can only migrate files whose content is currently available. Other
files will be skipped.
After migrating a file to a new backend, the old content in the old backend
will still be present. That is necessary because multiple files
can point to the same content. The `git annex unused` subcommand can be
used to clear up that detritus later. Note that hard links are used,
to avoid wasting disk space.