[PATCH] commit: document a couple of options
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Jun 8, 2012, 10:18 UTC
- Message-ID
- <1339150710-12281-1-git-send-email-artagnon@gmail.com>
Document git commit '--branch' and '--no-post-rewrite'. Mention that '-z' can also be spelt as '--null'.
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com> --- I noticed this while reading through builtin/commit.c.
Documentation/git-commit.txt | 8 ++++++++ 1 file changed, 8 insertions(+)
diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt index 2d695f6..f400835 100644 --- a/Documentation/git-commit.txt +++ b/Documentation/git-commit.txt @@ -101,12 +101,16 @@ OPTIONS When doing a dry-run, give the output in the short-format. See linkgit:git-status[1] for details. Implies `--dry-run`. +--branch:: + Show the branch and tracking info even in short-format. + --porcelain:: When doing a dry-run, give the output in a porcelain-ready format. See linkgit:git-status[1] for details. Implies `--dry-run`. -z:: +--null:: When showing `short` or `porcelain` status output, terminate entries in the status output with NUL, instead of LF. If no format is given, implies the `--porcelain` output format. @@ -189,6 +193,10 @@ OPTIONS current tip -- if it was a merge, it will have the parents of the current tip as parents -- so the current top commit is discarded. + +--no-post-rewrite:: + Bypass the post-rewrite hook. + + -- It is a rough equivalent for:
-- 1.7.10