From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/PROBLEMS] Document the QUIT problem
Date: Fri, 20 Feb 2004 18:13:00 -0000 [thread overview]
Message-ID: <20040220181318.751764B104@berman.michael-chastain.com> (raw)
Err, your ChangeLog entry says "NEWS" instead of "PROBLEMS".
Also I would like to have a PR for the problem.
To me, the PR's are the nexus of information about known problems
with gdb.
That's just my opinion -- Eli Z is in charge of doco.
Michael C
===
2004-02-20 J. brobecker <brobecker@gnat.com>
* NEWS: Document a known problem.
next reply other threads:[~2004-02-20 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 18:13 Michael Elizabeth Chastain [this message]
2004-02-20 21:48 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2004-02-20 17:32 Joel Brobecker
2004-02-20 17:55 ` Eli Zaretskii
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=20040220181318.751764B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@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