From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: "'Daniel Jacobowitz'" <drow@false.org>, <gdb-patches@sourceware.org>
Subject: Re: PING : [PING] [RFC-v2] Use untested for macscp.exp if no macro information generated
Date: Fri, 29 May 2009 23:40:00 -0000 [thread overview]
Message-ID: <m3tz33xyuv.fsf@fleche.redhat.com> (raw)
In-Reply-To: <000d01c9d22b$9823cec0$c86b6c40$@u-strasbg.fr> (Pierre Muller's message of "Mon\, 11 May 2009 13\:28\:21 +0200")
>>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
Pierre> I would still like to have this accepted
Pierre> even if it is not optimal...
Pierre> In the sense that you still get one failure for
Pierre> gcc-3 using stabs as default debugging info format
Pierre> instead of about 500.
I was intending to try to rewrite this so that we would not see any
FAILs, but I am finally admitting I will not get to this :)
This patch is ok. Thanks.
Tom
next prev parent reply other threads:[~2009-05-29 23:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 11:37 Results of macscp.exp test on cygwin Pierre Muller
2008-10-09 16:29 ` Tom Tromey
2008-10-09 16:46 ` Pedro Alves
2008-10-09 18:14 ` Daniel Jacobowitz
2008-10-09 20:21 ` Michael Snyder
2008-10-09 22:28 ` Paul Pluzhnikov
2008-10-10 16:04 ` [RFC] " Pierre Muller
2009-01-26 9:13 ` [PING] " Pierre Muller
2009-01-28 13:32 ` [RFC] Use untested for macscp.exp if no macro information generated Pierre Muller
2009-02-01 18:28 ` Daniel Jacobowitz
2009-02-03 14:36 ` [RFC-v2] " Pierre Muller
2009-02-18 22:59 ` [PING] " Pierre Muller
2009-02-19 8:20 ` Tom Tromey
2009-02-20 10:08 ` Pierre Muller
2009-05-11 11:30 ` PING : " Pierre Muller
2009-05-29 23:40 ` Tom Tromey [this message]
2009-05-30 8:04 ` Pierre Muller
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=m3tz33xyuv.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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