This is the mail archive of the
mailing list for the GCC project.
Re: Updating "regression hunting" to the Git world (was: [wwwdocs] Adjustments of "regression hunting" instructions to the post-SVN world.)
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 20 Jan 2020 14:49:54 +0000
- Subject: Re: Updating "regression hunting" to the Git world (was: [wwwdocs] Adjustments of "regression hunting" instructions to the post-SVN world.)
- References: <alpine.LSU.firstname.lastname@example.org>
On Sun, 19 Jan 2020 at 13:07, Gerald Pfeifer wrote:
> On Sun, 19 Jan 2020, Gerald Pfeifer wrote (on gcc-patches@):
> > With Git a clone carries the whole repository, so remove instructions
> > on obtaining a local copy of the repository and related instructions
> > on SVN usage.
> I just updated https://gcc.gnu.org/bugs/reghunt.html , mostly by
> removing obsolete aspects related to SVN:
> If you have further updates to that page, please go ahead and
> simply make them (or let me know).
It still says "The following SVN commands are ..."
> Also contrib/reghunt appears in need of *quite* some updates.
> Or do we want to retire it?
I've never read that web page or looked at contrib/reghunt before, but
most of it can probably be done by 'git bisect' run. The web page
should be rewritten in terms of using git bisect. I can take a stab at
that if nobody else wants to.
It's possible that the various contrib/reghunt/bin/gcc-test-* helper
scripts could still be useful with 'git bisect run' as the building
blocks for a script that checks a given revision.