diff options
| author |  Joey Hess <joey@kitenet.net> | 2013-07-03 15:26:59 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2013-07-03 15:26:59 -0400 |
| commit | 289a3f7749a5086a19a22b277a022e3b006da94f (patch) | |
| tree | 10c4a4fe5ab4391c82cf91f4069bf0d7f4c7490b /doc | |
| parent | 0e4ed4dd9bf9b78c1723400e9c787a18430c5f57 (diff) | |
--unused: New switch that makes git-annex operate on all data found by the last run of git annex unused. Supported by fsck, get, move, copy.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/git-annex.mdwn | 11 | ||||
| -rw-r--r-- | doc/walkthrough/unused_data.mdwn | 9 |
2 files changed, 18 insertions, 2 deletions
diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn index 012b7595c..0f63edf94 100644 --- a/doc/git-annex.mdwn +++ b/doc/git-annex.mdwn @@ -380,6 +380,12 @@ subdirectories). To check for annexed data on a remote, specify --from. + After running this command, you can use the --unused option to + operate on all the unused data that was found. For example, to + move all unused data to origin: + + git annex unused; git annex move --unused --to origin + * dropunused [number|range ...] Drops the data corresponding to the numbers, as listed by the last @@ -610,6 +616,11 @@ subdirectories). normal behavior is to only operate on specified files in the working tree. +* --unused + + Operate on all data that has been determined to be unused by + a previous run of git-annex unused. + * --quiet Avoid the default verbose display of what is done; only show errors diff --git a/doc/walkthrough/unused_data.mdwn b/doc/walkthrough/unused_data.mdwn index 63fb9f66d..7e910b5f5 100644 --- a/doc/walkthrough/unused_data.mdwn +++ b/doc/walkthrough/unused_data.mdwn @@ -5,8 +5,7 @@ file, the old content of the file remains in the annex. Another way is when migrating between key-value [[backends]]. This might be historical data you want to preserve, so git-annex defaults to -preserving it. So from time to time, you may want to check for such data and -eliminate it to save space. +preserving it. So from time to time, you may want to check for such data: # git annex unused unused . (checking for unused data...) @@ -28,3 +27,9 @@ data anymore, you can easily remove it: Hint: To drop a lot of unused data, use a command like this: # git annex dropunused 1-1000 + +Rather than removing the data, you can instead send it to other +repositories: + + # git annex copy --unused --to backup + # git annex move --unused --to archive |