Merge branch 'cn/commit-amend-doc' into maint
* cn/commit-amend-doc: Documentation/git-commit: reword the --amend explanation
This commit is contained in:
commit
788e98f8c0
@ -207,14 +207,15 @@ variable (see linkgit:git-config[1]).
|
|||||||
without changing its commit message.
|
without changing its commit message.
|
||||||
|
|
||||||
--amend::
|
--amend::
|
||||||
Used to amend the tip of the current branch. Prepare the tree
|
Replace the tip of the current branch by creating a new
|
||||||
object you would want to replace the latest commit as usual
|
commit. The recorded tree is prepared as usual (including
|
||||||
(this includes the usual -i/-o and explicit paths), and the
|
the effect of the `-i` and `-o` options and explicit
|
||||||
commit log editor is seeded with the commit message from the
|
pathspec), and the message from the original commit is used
|
||||||
tip of the current branch. The commit you create replaces the
|
as the starting point, instead of an empty message, when no
|
||||||
current tip -- if it was a merge, it will have the parents of
|
other message is specified from the command line via options
|
||||||
the current tip as parents -- so the current top commit is
|
such as `-m`, `-F`, `-c`, etc. The new commit has the same
|
||||||
discarded.
|
parents and author as the current one (the `--reset-author`
|
||||||
|
option can countermand this).
|
||||||
+
|
+
|
||||||
--
|
--
|
||||||
It is a rough equivalent for:
|
It is a rough equivalent for:
|
||||||
|
Loading…
Reference in New Issue
Block a user