summaryrefslogtreecommitdiff
path: root/doc/git-annex-add.mdwn
Commit message (Collapse)AuthorAge
* doc updateGravatar Joey Hess2015-12-15
|
* fix incorrect doc changeGravatar Joey Hess2015-12-15
|
* update doc for v6Gravatar Joey Hess2015-12-15
|
* -J for add/addurl/importGravatar Joey Hess2015-11-05
|
* add: Stage symlinks the same as git add would, even if they are not a link ↵Gravatar Joey Hess2015-07-07
| | | | to annexed content.
* expand manpages cross-references significantlyGravatar Antoine Beaupré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.
* add: If annex.largefiles is set and does not match a file that's being ↵Gravatar Joey Hess2015-04-08
| | | | 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.
* splitting up the man pageGravatar Joey Hess2015-03-23
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..