This is the mail archive of the
mailing list for the GCC project.
Re: Moving to git
- From: Jason Merrill <jason at redhat dot com>
- To: Joseph Myers <joseph at codesourcery dot com>, "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: ramrad01 at arm dot com, Jonathan Wakely <jwakely dot gcc at gmail dot com>, Jeff Law <law at redhat dot com>, "gcc at gnu dot org" <gcc at gnu dot org>, Jakub Jelinek <jakub at redhat dot com>
- Date: Fri, 21 Aug 2015 14:07:21 -0400
- Subject: Re: Moving to git
- Authentication-results: sourceware.org; auth=none
- References: <55D61512 dot 8010002 at redhat dot com> <55D61B23 dot 3000309 at redhat dot com> <55D63403 dot 4000603 at redhat dot com> <CAJA7tRahuaA36w76YD0nE+6ur1Y8T1ThZ8ssSmGgRmzT9bUcBA at mail dot gmail dot com> <CAH6eHdTcMMgHBax=x42aAE+LdRyKnzNhaLxvc_VcPQVP_P7nog at mail dot gmail dot com> <CAJA7tRYwEMxTrFmFNYg0Mh9QTLyNOtVPH7kjjSTzS82RPyXHfQ at mail dot gmail dot com> <CAMe9rOpV3G_=ZFWiyRk9bThXEA=_JUJrqEi8hmqLW0hKZLUhqg at mail dot gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1508211523410 dot 2039 at digraph dot polyomino dot org dot uk>
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.