From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: GDB `cannotfix' pr state, require PR with xfail `moving forward'.
Date: Fri, 17 Jan 2003 20:52:00 -0000 [thread overview]
Message-ID: <200301172052.h0HKqde07171@duracef.shout.net> (raw)
mec> ... you are talking
mec> about 's/CLLbsNNNNN//', not 'g/CLLbsNNNNN/d'.
mec>
mec> I still think that's not useful in light of the progress we are
mec> making but I would not be opposed to it happening.
andrewc> `useful' doesn't come into this part of the equation.
andrewc> Those references to an external bug database need to be removed.
andrewc> The only thing up for negotiation on this one is the timing.
Pedantically: I mean it's not useful, for the goal of cleaning up
xfails, to purge the CLLbs.
For the goal of cleaning up dangling references it's very useful.
I'll get out of my damn mailer and go purge those bad boys from
gdb.c++/*.exp right now.
Michael C
talking too much, maintaining too little :-/
next reply other threads:[~2003-01-17 20:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 20:52 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 20:28 Michael Elizabeth Chastain
2003-01-18 11:33 ` Eli Zaretskii
2003-01-17 20:03 Michael Elizabeth Chastain
2003-01-17 19:57 Michael Elizabeth Chastain
2003-01-17 19:45 Michael Elizabeth Chastain
2003-01-17 19:46 ` Daniel Jacobowitz
2003-01-17 20:12 ` Andrew Cagney
2003-01-17 20:18 ` Daniel Jacobowitz
2003-01-17 20:53 ` Andrew Cagney
2003-01-17 22:06 ` Daniel Jacobowitz
2003-01-17 23:28 ` Andrew Cagney
2003-01-18 3:40 ` Daniel Jacobowitz
2003-01-17 20:16 ` Andrew Cagney
2003-01-16 19:35 Andrew Cagney
2003-01-17 19:26 ` Andrew Cagney
2003-01-17 19:29 ` Daniel Jacobowitz
2003-01-17 19:47 ` Andrew Cagney
2003-01-17 19:40 ` David Carlton
2003-01-17 19:56 ` Andrew Cagney
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=200301172052.h0HKqde07171@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=gdb@sources.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