From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com
Cc: gdb@sources.redhat.com
Subject: Re: When may I close a 5.1.1 PR?
Date: Mon, 11 Feb 2002 18:54:00 -0000 [thread overview]
Message-ID: <200202120254.g1C2sPg30970@duracef.shout.net> (raw)
Andrew Cagney writes:
> I'm just happy to see the problem and fix recorded. Probably close it
> since I assume no one has any intention of fixing it on the branch.
That works for me. I'll review some more of the open bugs and see
if they are fixed in HEAD now.
> I was thinking that it should just jump to the bug database. However,
> looking around I've noticed that other projects have (for an equivalent
> page) used it to ``educate'' the reader as to how to submit a better bug
> report and where to find potential fixes.. I'm not sure we want to go
> down that path.
I like this idea. We see a lot of reports that do not include the
target architecture or the version string. Also it's very useful to
see what compiler the user built their program with.
It's a service to us if the bug reports are better to begin with.
It would be a service to the users if we say: if your gdb is version
4.18 or 5.0, then you should upgrade to 5.1.1 or the latest CVS version
before sending a letter at all.
Michael C
next reply other threads:[~2002-02-12 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 18:54 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-10 18:05 Michael Elizabeth Chastain
2002-02-10 22:43 ` Eli Zaretskii
2002-02-11 9:24 ` 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=200202120254.g1C2sPg30970@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@cygnus.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