3 ms·
Nice article but the author should avoid making sweeping generalizations like the one in the very beginning: they state that they haven’t “found a case where [c
by SOLAR_FIELDS 9y ago
Nice article but the author should avoid making sweeping generalizations like the one in the very beginning: they state that they haven’t “found a case where [cherry-picking is] actually good.” They then go on to detail a specific place where cherry picking doesn’t make sense (and I agree with the author in that specific case) but I can easily imagine several scenarios where it makes more sense to cherry-pick.
Consider the following as an example. You cut a release branch, and after that branch you realize a bug and fix it on master. Turns out that bug later is more critical than previously thought, so what better way to pull it down to the release branch than a cherry-pick?
- number6 9y agoYou add some print messages for debugging. you make a commit. fix around ... revert ... fix around ... you caught the bug! Nice now commit and cherry pick it into master. Why would I want to merge all the print messages?
- ksk 9y ago>Nice article but the author should avoid making sweeping generalizations like the one in the very beginning: How is it a sweeping generalization to say that they personally haven't found something useful?
- draw_down 9y agoPeople just like to rail against "sweeping generalizations", that's all. You know, you're the black-and-white dumb guy and I'm the intelligent nuanced guy.