Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> you might as well rebase or cherry-pick

Both tools are pure vandalism compared to merge. Among the two, cherry-picking is preferable in this case because you're "only" destroying your own history, so in the end, it's your funeral.

> Developer end up fixing additional issues in the merge commit instead of actual commits.

A merge commit IS an actual commit, in every sense of the word. The notion it somehow isn't, is what you need to get rid of.



Rebasing / rerolling is completely fine if done right, no need to be overly zealous. But merges are often more elegant




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: