I'm working on 2 different branches: release and development.
I noticed I still need to integrate some changes that were committed to the release branch back into the development branch.
The problem is I don't need all of the commit, only some hunks in certain files, so a simple
git cherry-pick bc66559
does not do the trick.
When I do a
git show bc66559
I can see the diff but don't really know a good way of applying that partially to my current working tree.
The core thing you're going to want here is
git add -p (
-p is a synonym for
--patch). This provides an interactive way to add in content, letting you decide whether each hunk should go in or not, and even letting you manually edit the patch if necessary.
To use it in combination with cherry-pick:
git cherry-pick -n <commit> # get your patch, but don't commit (-n = --no-commit)
git reset # unstage the changes from the cherry-picked commit
git add -p # make all your choices (add the changes you do want)
git commit # make the commit!
(Thanks to Tim Henigan for reminding me that
git-cherry-pick has a
--no-commit option, and thanks to Felix Rabe for pointing out that you need to
git reset. If you only want to leave a few things out of the commit, you could use
git reset <path>... to unstage just those files.)
You can provide specific paths to
add -p if necessary. If you're starting with a patch you could replace the
If you really want to
git cherry-pick -p <commit> (that option does not exist), you can use
git checkout -p <commit>
That will diff the current commit against the commit you specify, and allow you to apply hunks from that diff individually. This option may be more useful if the commit you're pulling in has merge conflicts in part of the commit you're not interested in. (Note, however, that
checkout differs from
checkout tries to apply
<commit>'s contents entirely, while
cherry-pick applies the diff of the specified commit from it's parent. This means that
checkout can apply more than just that commit, which might be more than you want.)