From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Mike Stump <mikestump@comcast.net>,
gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: Mirror gcc/contrib -> src/contrib? [was Re: [patch, gcc RFA] dg-extract-results.sh: Handle KFAILs.]
Date: Mon, 09 Apr 2012 14:55:00 -0000 [thread overview]
Message-ID: <CADPb22TwTpVJoSJsHRRcTTE=oKaG4N3qHqW44JV-qEzJVhL5kg@mail.gmail.com> (raw)
In-Reply-To: <878vi5aruu.fsf@fleche.redhat.com>
On Mon, Apr 9, 2012 at 7:43 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> On Thu, Mar 15, 2012 at 11:54 AM, Mike Stump <mikestump@comcast.net> wroteDoug> btw, is there any interest in mirroring gcc/contrib -> src/contrib?
> Doug> [instead of gdb having its own copy in gdb/testsuite, it *could* use
> Doug> the one in, e.g., src/contrib. I don't have a strong opinion. I'm
> Doug> just looking for others opinions, as the topic came up in another
> Doug> context.]
>
> I wouldn't mind if anything else there was useful for gdb.
There's testsuite-management/validate_failures.py which is useful
here. Whether it's useful to the FSF or Redhat trees, I don't know.
I can't put in the time to do all the administrivia to make this
happen (and keep it working, e.g., impose something like making sure
people follow the same rules as libiberty so the trees stay in sync),
so I don't want to send people down this path unless there's
sufficient support, and someone else to do the work.
next prev parent reply other threads:[~2012-04-09 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 19:45 Doug Evans
2012-04-09 14:43 ` Tom Tromey
2012-04-09 14:55 ` Doug Evans [this message]
2012-04-09 15:17 ` 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='CADPb22TwTpVJoSJsHRRcTTE=oKaG4N3qHqW44JV-qEzJVhL5kg@mail.gmail.com' \
--to=dje@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mikestump@comcast.net \
--cc=tromey@redhat.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