This is the mail archive of the
mailing list for the GCC project.
Re: Moving to git
- From: Andreas Schwab <schwab at linux-m68k dot org>
- 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 14:36:49 +0200
- 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>
Richard Biener <firstname.lastname@example.org> writes:
> 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.
You can surely bisect a fix, you just have to remember that bad means
fixed and good means unfixed. And of course, the git community is
working on enhancing the bisect UI for this use case.
Andreas Schwab, email@example.com
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."