diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-01-08 15:14:41 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-01-08 15:14:41 -0400 |
| commit | 32b0e103909035ad0f25427c57a1ff504aefcada (patch) | |
| tree | 92bcafa885e1c02795226c7c80c8174576e560ef /doc/walkthrough.mdwn | |
| parent | 82fe151f8796c5f0a37565134deb55142fdd1a99 (diff) | |
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.
Diffstat (limited to 'doc/walkthrough.mdwn')
| -rw-r--r-- | doc/walkthrough.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/walkthrough.mdwn b/doc/walkthrough.mdwn index 2f868e303..47f05ebcf 100644 --- a/doc/walkthrough.mdwn +++ b/doc/walkthrough.mdwn @@ -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 |