From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: eliz@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc/doco] bug reporting: mention 'script' command
Date: Sat, 19 Jun 2004 17:28:00 -0000 [thread overview]
Message-ID: <20040619172802.C33B34B104@berman.michael-chastain.com> (raw)
Committed.
===
2004-06-17 Michael Chastain <mec.gnu@mindspring.com>
gdb.texinfo (Bug Reporting): Mention session recording,
with the script command or Emacs.
next reply other threads:[~2004-06-19 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 17:28 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 19:55 Michael Elizabeth Chastain
2004-06-19 8:32 ` Eli Zaretskii
2004-06-17 20:52 Michael Elizabeth Chastain
2004-06-18 18:36 ` 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=20040619172802.C33B34B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=eliz@gnu.org \
--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