{"thread":{"id":"38119","subject":"GIT: cherry-picking includes changes from a different commit","startedAt":"2014-12-05T20:04:28Z","lastAt":"2014-12-06T03:17:37Z","messageCount":2,"participants":["Ruud Huynen","Keith Amling"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"253183","messageId":"02f801d010c6$ad32a1d0$0797e570$@hispeed.ch","threadId":"38119","inReplyTo":null,"subject":"GIT: cherry-picking includes changes from a different commit","fromName":"Ruud Huynen","fromEmail":"ruud.huynen@hispeed.ch","sentAt":"2014-12-05T20:04:28Z","receivedAt":"2014-12-05T20:04:28Z","isPatch":false,"sender":{"key":"ruud.huynen@hispeed.ch","avatar":null},"body":"I noticed when cherry-picking a commit it includes changes from this commit\nand also changes from a different commit as the one I was picking.\n\nI was in contact with \"jast\" on IRC, who noticed the issue, but didn't had\ntime to look further.\n\nFor a description of my problem, please read\nhttp://stackoverflow.com/questions/27220638/git-cherry-pick-info-about-picke\nd-commits\n\n\ngit clone git://github.com/MythTV/mythtv.git\ngit checkout fixes/0.27\n\ngit cherry-pick 30df98ce5d11b69d0b5c5114a9007cdfc79a7e9b\n# from master\n# commit also picked: 17f17e1fc51b3b4017e08f5ea35c8a7b5a64eeec\n# resulting in a conflict\n\nFor the commits and before/conflict files, see\nhttps://gist.github.com/FritzHerbers/4f9b0990b6bca15a70eb\n\nAs nobody could believe me, that changes from another commit are included,\nis something wrong, or is it new behavior? Why did it happen?\nWith which command, can I have a listing of \"intermediate\" commits picked?\nHow can I automate such situations?\n\nFritz\ngit version 1.9.1\n"},{"id":"253227","messageId":"20141206031737.GB12663@gmail.com","threadId":"38119","inReplyTo":"02f801d010c6$ad32a1d0$0797e570$@hispeed.ch","subject":"Re: GIT: cherry-picking includes changes from a different commit","fromName":"Keith Amling","fromEmail":"keith.amling@gmail.com","sentAt":"2014-12-06T03:17:37Z","receivedAt":"2014-12-06T03:17:37Z","isPatch":false,"sender":{"key":"keith.amling@gmail.com","avatar":null},"body":"If you're referring to what 86ff53a7a178 has it has resolved the merge\nconflict in a way that is almost certainly wrong.  If you turn on diff3\nmarkers you can see that LHS deleted clone_test while RHS added a\nfunction right after it.  The correct resolution is to include RHS's new\nstuff but not that function whereas 86ff53a7a178 includes everything\nfrom the RHS side of the conflict marker (thus including/adding\nclone_test).\n\nKeith\n\nThus spake Ruud Huynen, at Fri, Dec 05, 2014 at 09:04:28PM +0100:\n> From: Ruud Huynen <ruud.huynen@hispeed.ch>\n> To: git@vger.kernel.org\n> Subject: GIT: cherry-picking includes changes from a different commit\n> Date: Fri, 5 Dec 2014 21:04:28 +0100\n> \n> I noticed when cherry-picking a commit it includes changes from this commit\n> and also changes from a different commit as the one I was picking.\n> \n> I was in contact with \"jast\" on IRC, who noticed the issue, but didn't had\n> time to look further.\n> \n> For a description of my problem, please read\n> http://stackoverflow.com/questions/27220638/git-cherry-pick-info-about-picke\n> d-commits\n> \n> \n> git clone git://github.com/MythTV/mythtv.git\n> git checkout fixes/0.27\n> \n> git cherry-pick 30df98ce5d11b69d0b5c5114a9007cdfc79a7e9b\n> # from master\n> # commit also picked: 17f17e1fc51b3b4017e08f5ea35c8a7b5a64eeec\n> # resulting in a conflict\n> \n> For the commits and before/conflict files, see\n> https://gist.github.com/FritzHerbers/4f9b0990b6bca15a70eb\n> \n> As nobody could believe me, that changes from another commit are included,\n> is something wrong, or is it new behavior? Why did it happen?\n> With which command, can I have a listing of \"intermediate\" commits picked?\n> How can I automate such situations?\n> \n> Fritz\n> git version 1.9.1\n> \n> \n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"}]}