1GIT-CHERRY-PICK(1)                Git Manual                GIT-CHERRY-PICK(1)
2
3
4

NAME

6       git-cherry-pick - Apply the change introduced by an existing commit
7

SYNOPSIS

9       git-cherry-pick [--edit] [-n] [-x] <commit>
10

DESCRIPTION

12       Given one existing commit, apply the change the patch introduces, and
13       record a new commit that records it. This requires your working tree to
14       be clean (no modifications from the HEAD commit).
15

OPTIONS

17       <commit>
18           Commit to cherry-pick. For a more complete list of ways to spell
19           commits, see "SPECIFYING REVISIONS" section in git-rev-parse(1).
20
21       -e|--edit
22           With this option, git-cherry-pick will let you edit the commit
23           message prior committing.
24
25       -x
26           Cause the command to append which commit was cherry-picked after
27           the original commit message when making a commit. Do not use this
28           option if you are cherry-picking from your private branch because
29           the information is useless to the recipient. If on the other hand
30           you are cherry-picking between two publicly visible branches (e.g.
31           backporting a fix to a maintenance branch for an older release from
32           a development branch), adding this information can be useful.
33
34       -r
35           It used to be that the command defaulted to do -x described above,
36           and -r was to disable it. Now the default is not to do -x so this
37           option is a no-op.
38
39       -n|--no-commit
40           Usually the command automatically creates a commit with a commit
41           log message stating which commit was cherry-picked. This flag
42           applies the change necessary to cherry-pick the named commit to
43           your working tree, but does not make the commit. In addition, when
44           this option is used, your working tree does not have to match the
45           HEAD commit. The cherry-pick is done against the beginning state of
46           your working tree.
47
48           This is useful when cherry-picking more than one commits´ effect to
49           your working tree in a row.
50

AUTHOR

52       Written by Junio C Hamano <junkio@cox.net>
53

DOCUMENTATION

55       Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
56

GIT

58       Part of the git(7) suite
59
60
61
62
63Git 1.5.3.3                       10/09/2007                GIT-CHERRY-PICK(1)
Impressum