| Commit message (Collapse) | Author | Age |
|
|
|
| |
mdwn2man gets confused as `command` spanning multiple lines..
|
|
|
|
|
|
|
| |
* add, addurl, import, importfeed: When in a v6 repository on a crippled
filesystem, add files unlocked.
* annex.addunlocked: New configuration setting, makes files always be
added unlocked. (v6 only)
|
| |
|
|
|
|
| |
Include added key in output.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to annexed content.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
added, the file will be checked into git rather than being added to the annex. Previously, git annex add skipped over such files; this new behavior is more useful in direct mode.
|
|
Common command man pages all split out and often expanded.
A few sections split out into their own pages.
Still need to do all the other commands..
|