git-annex/doc/git-annex-addunused.mdwn

# NAME

git-annex addunused - add back unused files

# SYNOPSIS

git annex addunused `[number|range ...]`

# DESCRIPTION

Adds back files for the content corresponding to the numbers or ranges,
as listed by the last `git annex unused`. 

The files will have names starting with "unused."

# SEE ALSO

[[git-annex]](1)

[[git-annex-add]](1)

[[git-annex-unused]](1)

# AUTHOR

Joey Hess <id@joeyh.name>

Warning: Automatically converted into a man page by mdwn2man. Edit with care.
separated man pages for all the maintenance commands 2015-03-24 19:23:59 +00:00			`# NAME`

			`git-annex addunused - add back unused files`

			`# SYNOPSIS`

			git annex addunused `[number\|range ...]`

			`# DESCRIPTION`

			`Adds back files for the content corresponding to the numbers or ranges,`
			as listed by the last `git annex unused`.

			`The files will have names starting with "unused."`

			`# SEE ALSO`

			`[[git-annex]](1)`

expand manpages cross-references significantly i found that most man pages only had references to the main git-annex manpage, which i stillfind pretty huge and hard to navigate through. i tried to sift through all the man pages and add cross-references between relevant pages. my general rule of thumb is that links should be both ways unless one of the pages is a more general page that would become ridiculously huge if all backlinks would be added (git-annex-preferred-content comes to mind). i have also make the links one per line as this is how it was done in the metadata pages so far. i did everything but the plumbing, utility and test commands, although some of those are linked from the other commands so cross-links were added there as well. 2015-05-29 16:12:55 +00:00			`[[git-annex-add]](1)`

			`[[git-annex-unused]](1)`

separated man pages for all the maintenance commands 2015-03-24 19:23:59 +00:00			`# AUTHOR`

			`Joey Hess <id@joeyh.name>`

			`Warning: Automatically converted into a man page by mdwn2man. Edit with care.`