On 08/21/2015 11:26 AM, Joseph Myers wrote:
On Fri, 21 Aug 2015, H.J. Lu wrote:
Can we enforce that "git bisect" must work on official branches?
I think a good principle independent of moving to git is that commits
should be bisectable. In particular, if a patch series is committed as
separate commits, each commit should be intended to leave the tree in a
working state; if a change was split up purely for review purposes rather
than with each subset 1-N of the patches intended to leave a working tree,
combine the changes before committing.
Yes. But if there was a merge from a feature branch that doesn't
achieve this (as I expect many don't, in early WIP stages), then you can
tell bisect to avoid descending into other branches.
https://stackoverflow.com/questions/5638211/how-do-you-get-git-bisect-to-ignore-merged-branches
Jason
