From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Updating "regression hunting" to the Git world (was: [wwwdocs] Adjustments of "regression hunting" instructions to the post-SVN world.)
Date: Mon, 20 Jan 2020 18:50:00 -0000 [thread overview]
Message-ID: <CAH6eHdQtka7WvQE_u4TyBNqpt0REFjv50qPPK4qPOW0QkoemFw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2001191402190.739@anthias.pfeifer.com>
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:
>
> https://gcc.gnu.org/ml/gcc-patches/2020-01/msg01121.html
>
>
> 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.
next prev parent reply other threads:[~2020-01-20 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 11:21 Gerald Pfeifer
2020-01-20 18:50 ` Jonathan Wakely [this message]
2020-01-21 13:51 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH6eHdQtka7WvQE_u4TyBNqpt0REFjv50qPPK4qPOW0QkoemFw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).