Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | enableremote: Remove annex-ignore configuration from a remote. | 2016-05-24 | |
| | |||
* | enableremote: Can now be used to explicitly enable git-annex to use git ↵ | 2016-05-24 | |
| | | | | remotes. Using the command this way prevents other git-annex commands from probing new git remotes to auto-enable them. | ||
* | enableremote: List uuids and descriptions of remotes that can be enabled, ↵ | 2015-10-26 | |
| | | | | and accept either the uuid or the description in leu if the name. | ||
* | Special remotes configured with autoenable=true will be automatically ↵ | 2015-09-14 | |
| | | | | enabled when git-annex init is run. | ||
* | expand manpages cross-references significantly | 2015-05-29 | |
| | | | | | | | | | | | | | | | | | | 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. | ||
* | separated man pages for all the setup commands while at the gate in ATL | 2015-03-23 | |