3 ms·
Why do you want to review branches? Doesn't that encourage longer divergence, therefore decreasing the percentage of atomic commits and increasing the risk of e
by peterhunt 12y ago
Why do you want to review branches? Doesn't that encourage longer divergence, therefore decreasing the percentage of atomic commits and increasing the risk of every merge?
- deng 12y agoThe issues you name are certainly valid, and I would only recommend this with a VCS that offers a wide range of possibilities for rewriting history. In the ideal case, a feature branch is a unit which implements a feature, fixes a bug, etc., and is usually comprised of several commits to achieve that. The advantage is that you clearly see the steps needed for achieving the desired result, each with its own commit log, and arranged in a logical order. Of course, you can do this with a set of patches as well, but then you need tooling separate from your VCS to manage that. Git has excellent support for re-arranging your commits, splitting/combining them, rebasing them onto current HEAD or onto some version branch.