summaryrefslogtreecommitdiff
path: root/doc/git-annex-whereis.mdwn
Commit message (Collapse)AuthorAge
* --branch, stage 1Gravatar Joey Hess2016-07-20
| | | | | | | | | | | | | | | | Added --branch option to copy, drop, fsck, get, metadata, mirror, move, and whereis commands. This option makes git-annex operate on files that are included in a specified branch (or other treeish). The names of the files from the branch that are being operated on are not displayed yet; only the keys. Displaying the filenames will need changes to every affected command. Also, note that --branch can be specified repeatedly. This is not really documented, but seemed worth supporting, especially since we may later want the ability to operate on all branches matching a refspec. However, when operating on two branches that contain the same key, that key will be operated on twice.
* whereis --batchGravatar Joey Hess2016-01-20
|
* 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.
* both whereis and metadata accept --key, --all, and --unused; document thatGravatar Joey Hess2015-04-21
|
* finished splitting out man pages for all commandsGravatar Joey Hess2015-03-25
|
* separated man pages for all the maintenance commandsGravatar Joey Hess2015-03-24