commit: fixup misplacement of --no-post-rewrite description

In e858af6 (commit: document a couple of options) the description of the
--no-post-rewrite option was put inside the paragraph for the --amend
option.  Move it down after the paragraph.

Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
Signed-off-by: Jeff King <peff@peff.net>

diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index 441c2087b98f4efe6b9f3f44fa7314bb3e14ac35..9e327cf5c0921e9c7c3a7858b216ef276d4eaf71 100644 (file)
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -193,10 +193,6 @@ 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.
        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:
 +
 --
 It is a rough equivalent for:


@@ -213,6 +209,9 @@ You should understand the implications of rewriting history if you
 amend a commit that has already been published.  (See the "RECOVERING
 FROM UPSTREAM REBASE" section in linkgit:git-rebase[1].)
 
 amend a commit that has already been published.  (See the "RECOVERING
 FROM UPSTREAM REBASE" section in linkgit:git-rebase[1].)
 

+--no-post-rewrite::
+       Bypass the post-rewrite hook.
+

 -i::
 --include::
        Before making a commit out of staged contents so far,
 -i::
 --include::
        Before making a commit out of staged contents so far,