git cherry-pick picks too muchContent on this page is from Stackoverflow
Has anybody else figured out strange behavior of
I have a big repository and just cherry picked a commit from another branch. The cherry picking resulted in conflicts. Then when resolving the conflicts I saw that the cherry pick introduced changes that where not made by the commit I picked nor part of
Could somebody please explain how git is working here? When does git pick more than the actual changes that where introduced by the commit to pick?
The file may diverged a lot in both branches..
My problem is less the current conflict but more that I might picked changes in the past that shouldn't come into that branch because git decided to introduce older changes too.
I'm sorry for the confusion, but by now I'm really confused and need help understanding what git did here..
So my main question is, should I worry about cherry picks that git didn't complain about? Can I be sure that git just picked the changes introduced by the commit to pick?
And the second question is: When does git put changes into the conflict state of the file that where neither part of the
HEAD file nor part of the commit to pick.
Thanks in advance!
View Local Answers... Can't find the answer to this question?
No answers yet.
Can you answer this question?
git cherry-pick picks too much
Can you answer these?
- Answer Draw Venn diagram using java
- Answer Turn String aaaabbbbddd into a4b4d3
- Answer Quick ways to optimize PHP code
- Answer run a batch file that would delete files in a folder (and its sub folders) that are older then 30 days
- Answer Is it possible to creat variables in foreach using the $key?
- Answer how can i fill the transparent area of the image when my finger moved on
- Answer Make a <td> as wide as possible
- Answer Converting raw SQL to Django QuerySet API
- Answer No perspective when using CATransform3DMakeRotation
- Answer How to send bufferedImage from JAVA to PHP