From: Doug Evans <dje@google.com>
To: Mike Stump <mikestump@comcast.net>
Cc: gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Mirror gcc/contrib -> src/contrib? [was Re: [patch, gcc RFA] dg-extract-results.sh: Handle KFAILs.]
Date: Fri, 06 Apr 2012 19:45:00 -0000 [thread overview]
Message-ID: <CADPb22RbR0Y5a_Xeah0NgO1jt=i0TFPfkgf6HXjCoebci-qVXQ@mail.gmail.com> (raw)
On Thu, Mar 15, 2012 at 11:54 AM, Mike Stump <mikestump@comcast.net> wrote:
> On Mar 15, 2012, at 11:09 AM, Pedro Alves wrote:
>> Still, kfail is standard DejaGnu, not a GDB invention. It'd be nice not to
>> need to fork the script for this.
>
> The change is fine for the gcc tree.
Committed (to the gcc tree, already in gdb tree).
Thanks.
btw, is there any interest in mirroring gcc/contrib -> src/contrib?
[instead of gdb having its own copy in gdb/testsuite, it *could* use
the one in, e.g., src/contrib. I don't have a strong opinion. I'm
just looking for others opinions, as the topic came up in another
context.]
next reply other threads:[~2012-04-06 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 19:45 Doug Evans [this message]
2012-04-09 14:43 ` Tom Tromey
2012-04-09 14:55 ` Doug Evans
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='CADPb22RbR0Y5a_Xeah0NgO1jt=i0TFPfkgf6HXjCoebci-qVXQ@mail.gmail.com' \
--to=dje@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mikestump@comcast.net \
/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