From: Don Howard <dhoward@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [patch] Minor doc tweak.
Date: Tue, 09 Jul 2002 10:23:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0207090856050.2913-100000@theotherone> (raw)
In-Reply-To: <Pine.SUN.3.91.1020709082838.11683F-100000@is>
On Tue, 9 Jul 2002, Eli Zaretskii wrote:
>
> On Mon, 8 Jul 2002, Don Howard wrote:
>
> > Add a little more info about the behavior of sourced command files.
>
> Thanks.
>
Comitted.
--
dhoward@redhat.com
gdb engineering
prev parent reply other threads:[~2002-07-09 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 16:24 Don Howard
2002-07-09 1:29 ` Eli Zaretskii
2002-07-09 10:23 ` Don Howard [this message]
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=Pine.LNX.4.33.0207090856050.2913-100000@theotherone \
--to=dhoward@redhat.com \
--cc=eliz@is.elta.co.il \
--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