diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-04-02 20:59:41 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-04-02 21:35:02 -0400 |
| commit | 868300d4c1dafd2c4b91ad3f369cfb48f14bb82a (patch) | |
| tree | 6108bc12c88d54be0763dc6e5cdc382461a9667c /doc/special_remotes.mdwn | |
| parent | 09a16176dea5ef2a51e3a3d00d77180966c597d9 (diff) | |
unused/dropunused: support --from
Diffstat (limited to 'doc/special_remotes.mdwn')
| -rw-r--r-- | doc/special_remotes.mdwn | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/special_remotes.mdwn b/doc/special_remotes.mdwn index 09b751d0f..f4d479aa9 100644 --- a/doc/special_remotes.mdwn +++ b/doc/special_remotes.mdwn @@ -8,3 +8,26 @@ They cannot be used by other git commands though. * [[Amazon_S3]] * [[directory]] + +## Unused content on special remotes + +Over time, special remotes can accumulate file content that is no longer +referred to by files in git. Normally, unused content in the current +repository is found by running `git annex unused`. To detect unused content +on special remotes, instead use `git annex unused --from`. Example: + + $ git annex unused --from mys3 + unused (checking for unused data on mys3...) + Some annexed data on mys3 is not used by any files in this repository. + NUMBER KEY + 1 WORM-s3-m1301674316--foo + (To see where data was previously used, try: git log --stat -S'KEY') + (To remove unwanted data: git-annex dropunused --from mys3 NUMBER) + Please be cautious -- are you sure that the remote repository + does not use this data? + $ git annex dropunused --from mys3 1 + dropunused 12948 (from mys3...) ok + +Do be cautious when using this; it cannot detect if content in a remote +is used by that remote, or is the last copy of data that is used by +some *other* remote. |