21ec5872f4
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.
34 lines
669 B
Markdown
34 lines
669 B
Markdown
# NAME
|
|
|
|
git-annex status - show the working tree status
|
|
|
|
# SYNOPSIS
|
|
|
|
git annex status `[path ...]`
|
|
|
|
# DESCRIPTION
|
|
|
|
Similar to `git status --short`, this command displays the status of the files
|
|
in the working tree. Shows files that are not checked into git, files that have
|
|
been deleted, and files that have been modified.
|
|
|
|
Particularly useful in direct mode.
|
|
|
|
# OPTIONS
|
|
|
|
* `--json`
|
|
|
|
Enable JSON output. This is intended to be parsed by programs that use
|
|
git-annex. Each line of output is a JSON object.
|
|
|
|
# SEE ALSO
|
|
|
|
[[git-annex]](1)
|
|
|
|
git-status(1)
|
|
|
|
# AUTHOR
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|