summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: c32f749)
raw | patch | inline | side by side (parent: c32f749)
author | Ralf Wildenhues <Ralf.Wildenhues@gmx.de> | |
Sun, 21 Oct 2007 09:36:19 +0000 (11:36 +0200) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Mon, 22 Oct 2007 05:38:19 +0000 (01:38 -0400) |
Reword the first sentence of the description of -x, in order to
make it easier to read and understand.
Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
make it easier to read and understand.
Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Documentation/git-cherry-pick.txt | patch | blob | history |
index 47b1e8c2fcd567b7e9d673f2d3ff30c9c32a1b83..76a2edfd9b3665b4dbe8e3837c06737e7c5fd232 100644 (file)
message prior committing.
-x::
- Cause the command to append which commit was
- cherry-picked after the original commit message when
- making a commit. Do not use this option if you are
- cherry-picking from your private branch because the
- information is useless to the recipient. If on the
+ When recording the commit, append to the original commit
+ message a note that indicates which commit this change
+ was cherry-picked from. Append the note only for cherry
+ picks without conflicts. Do not use this option if
+ you are cherry-picking from your private branch because
+ the information is useless to the recipient. If on the
other hand you are cherry-picking between two publicly
visible branches (e.g. backporting a fix to a
maintenance branch for an older release from a