From: Daniel Jacobowitz <drow@mvista.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb@sources.redhat.com
Subject: Re: A few things we've been up to at Apple lately
Date: Sat, 09 Nov 2002 14:46:00 -0000 [thread overview]
Message-ID: <20021109224742.GB31584@nevyn.them.org> (raw)
In-Reply-To: <20021109121202.A542@molenda.com>
On Sat, Nov 09, 2002 at 12:12:02PM -0800, Jason Molenda wrote:
> Well anyway, it's an interesting different take on the problem. If
> we could get setup_kfail's added to the FSF sources, I we'd go for
> that. The only minor nit I see with kfail as it's implemented right
> now is that it prints "(PRMS: 3061801)" which could potentially confuse
> someone into thinking these bug reports are in the gdb PRMS database
> somewhere..
FYI, it is now. It's in DejaGNU 1.4.3.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-09 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 1:49 Jason Molenda
2002-11-09 6:06 ` Andrew Cagney
2002-11-09 12:12 ` Jason Molenda
2002-11-09 14:46 ` Daniel Jacobowitz [this message]
2002-11-09 14:52 ` Jason Molenda
2002-11-09 11:49 ` Klee Dienes
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=20021109224742.GB31584@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jason-swarelist@molenda.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