This is the mail archive of the
mailing list for the GCC project.
Re: Moving to git
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: Jason Merrill <jason at redhat 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 12:44:59 +0100
- 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> <CAFiYyc0MBF3SFa_UOvSK3YhTWWWSn4Q0J=P6TvedaC5pkd7NCg at mail dot gmail dot com> <CAH6eHdQ+=Qq6yD+tukcPRMp81--sjVsx8PtJzoOEy_L+bPH3dw at mail dot gmail dot com> <CAFiYyc0PqNj-4xs_Aq+LUiBmYdKR1P9pHGUD0V1POC-LcMOUAw at mail dot gmail dot com>
On 21 August 2015 at 12:25, Richard Biener wrote:
> On Fri, Aug 21, 2015 at 12:52 PM, Jonathan Wakely <email@example.com> wrote:
>> On 21 August 2015 at 09:26, Richard Biener wrote:
>>> Btw, I've done this once now and it kind of works. You need to write your
>>> tests in a way to support gits limited way of searching (the past has to be
>>> always good, the future bad) - I've tried to find a change that was _fixing_
>>> a problem, something that doesn't seem to be supported. Heh. Well,
>>> just "fixed" the test script.
>> I'm pretty sure you can have bad older than good, just not when you're
>> using git bisect run to automate it.
> The point was to use git bisect.
I assume you mean git bisect *run*, because otherwise what I said
stands :-) You can use 'git bisect good' and 'git bisect bad' in any