1git-annex-unused(1)         General Commands Manual        git-annex-unused(1)
2
3
4

NAME

6       git-annex-unused - look for unused file content
7

SYNOPSIS

9       git annex unused
10

DESCRIPTION

12       Checks the annex for data that does not correspond to any files present
13       in any tag or branch, or in the git index, and prints a  numbered  list
14       of the data.
15
16       After  running  this command, you can use the --unused option with many
17       other git-annex commands to operate on all the  unused  data  that  was
18       found.
19
20       For example, to move all unused data to origin:
21
22        git annex unused; git annex move --unused --to origin
23

OPTIONS

25       --fast
26
27              Only show unused temp and bad files.
28
29       --from=repository
30              Check for unused data that is located in a repository.
31
32              The  repository  should be specified using the name of a config‐
33              ured remote, or the UUID or description of a repository.
34
35       --used-refspec=+ref:-ref
36              By default, any data that the git index uses, or that  any  refs
37              in  the git repository point to is considered to be used. If you
38              only want to use some refs, you can use this option  to  specify
39              the ones to use. Data that is not in the specified refs (and not
40              used by the index) will then be considered unused.
41
42              See REFSPEC FORMAT below for details of the format of this  set‐
43              ting.
44
45              The  git configuration annex.used-refspec can be used to config‐
46              ure this in a more permanent fashion.
47
48       --json Enable JSON output. This is intended to be  parsed  by  programs
49              that use git-annex.
50
51       --json-error-messages
52              Messages that would normally be output to standard error are in‐
53              cluded in the JSON instead.
54
55       Also the git-annex-common-options(1) can be used.
56

REFSPEC FORMAT

58       The refspec format  for  --used-refspec  and  annex.used-refspec  is  a
59       colon-separated  list  of  additions  and removals of refs.  A somewhat
60       contrived example:
61
62        +refs/heads/*:+HEAD^:+refs/tags/*:-refs/tags/old-tag:reflog
63
64       This adds all refs/heads/ refs, as well  as  the  previous  version  of
65       HEAD.  It  also adds all tags, except for old-tag. And it adds all refs
66       from the reflog.
67
68       The default behavior is equivilant to --used-refspec=+refs/*:+HEAD
69
70       The refspec is processed by starting with an empty  set  of  refs,  and
71       walking the list in order from left to right.
72
73       Each  +  using a glob is matched against all relevant refs (a subset of
74       git show-ref) and all matching refs are added to the set.  For example,
75       "+refs/remotes/*" adds all remote refs.
76
77       Each  + without a glob adds the literal value to the set.  For example,
78       "+HEAD^" adds "HEAD^".
79
80       Each - is matched against the set of refs accumulated so far.  Any refs
81       with names that match are removed from the set.
82
83       "reflog"  adds  all  the refs from the reflog. This will make past ver‐
84       sions of files not be considered to be unused  until  the  ref  expires
85       from  the reflog (by default for 90 days). Note that this may make git-
86       annex unused take some time to complete, it if needs to check every ref
87       from the reflog.
88

SEE ALSO

90       git-annex(1)
91
92       git-annex-dropunused(1)
93
94       git-annex-addunused(1)
95
96       git-annex-whereused(1)
97

AUTHOR

99       Joey Hess <id@joeyh.name>
100
101                                                           git-annex-unused(1)
Impressum