2011-03-28 02:52:13 +00:00
|
|
|
Most [[backends]] can transfer data to and from configured git remotes.
|
|
|
|
|
Normally those remotes are normal git repositories (bare and non-bare),
|
|
|
|
|
that store the file contents in their own git annex directory.
|
|
|
|
|
|
|
|
|
|
But, git-annex also extends git's concept of remotes, with these special
|
|
|
|
|
types of remotes. These can be used just like any normal remote by git-annex.
|
|
|
|
|
They cannot be used by other git commands though.
|
|
|
|
|
|
2011-03-28 17:47:29 +00:00
|
|
|
* [[Amazon_S3]]
|
2011-03-30 17:18:46 +00:00
|
|
|
* [[directory]]
|
2011-04-03 00:59:41 +00:00
|
|
|
|
|
|
|
|
## 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.
|
