diff options
| author |  Joey Hess <joey@kitenet.net> | 2010-11-15 18:13:20 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2010-11-15 18:13:20 -0400 |
| commit | 354be7a00b76b1ee961fa31ba81905e1d8c172bd (patch) | |
| tree | dcc5ce55ee8a8a77e69b79c32194d91ae1d72b60 | |
| parent | 3a4e9398a1652b664fb17dc2072f4b85966dcb61 (diff) | |
on dropunused and unused
| -rw-r--r-- | debian/changelog | 4 | ||||
| -rw-r--r-- | doc/walkthrough.mdwn | 28 |
2 files changed, 30 insertions, 2 deletions
diff --git a/debian/changelog b/debian/changelog index cffa7bb26..b6a426d1f 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,9 +1,9 @@ git-annex (0.07) UNRELEASED; urgency=low * find: New subcommand. - * unused: New subcommand, finds unused data (the global part of fsck). + * unused: New subcommand, finds unused data. (Split out from fsck.) * dropunused: New subcommand, provides for easy dropping of unused keys - by number, as listed by unused subcommand. + by number, as listed by the unused subcommand. -- Joey Hess <joeyh@debian.org> Sun, 14 Nov 2010 12:34:49 -0400 diff --git a/doc/walkthrough.mdwn b/doc/walkthrough.mdwn index 1e07053ae..b6f322c49 100644 --- a/doc/walkthrough.mdwn +++ b/doc/walkthrough.mdwn @@ -277,6 +277,34 @@ add something like this to `.gitattributes`: * git-annex-backend=SHA1 +## unused data + +It's possible for data to accumulate in the annex that no files point to +nymore. One way it can happen is if you `git rm` a file without +first calling `git annex drop`. And, when you modify an annexed file, the old +content of the file remains in the annex. + +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. + + # git annex unused + unused (checking for unused data...) + Some annexed data is no longer pointed to by any files in the repository. + NUMBER KEY + 1 WORM:1289672605:3:file + 2 WORM:1289672605:14:file + (To see where data was previously used, try: git log --stat -S'KEY') + (To remove unwanted data: git-annex dropunused NUMBER) + failed + +After running `git annex unused`, you can follow the instructions to examine +the history of files that used the data, and if you decide you don't need that +data anymore, you can easily remove it: + + # git annex dropunused 1 + dropunused 1 ok + ## fsck: verifying your data You can use the fsck subcommand to check for problems in your data. |