From: Eli Zaretskii <eliz@elta.co.il>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: fix node name (revised patch)
Date: Wed, 29 Oct 2003 06:18:00 -0000 [thread overview]
Message-ID: <u8yn4zhzp.fsf@elta.co.il> (raw)
In-Reply-To: <vt2znflm3aa.fsf@zenia.home> (message from Jim Blandy on 28 Oct 2003 16:59:57 -0500)
> From: Jim Blandy <jimb@redhat.com>
> Date: 28 Oct 2003 16:59:57 -0500
>
> So there is no underlying problem in GDB's documentation build
> process; it is an anomaly introduced by our internal processes.
Thanks for looking into this.
next prev parent reply other threads:[~2003-10-29 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 2:41 RFA: fix node name Jim Blandy
2003-10-25 4:00 ` RFA: fix node name (revised patch) Jim Blandy
2003-10-25 13:02 ` Eli Zaretskii
2003-10-25 13:03 ` Eli Zaretskii
2003-10-28 22:00 ` Jim Blandy
2003-10-29 6:18 ` Eli Zaretskii [this message]
2003-10-25 13:00 ` RFA: fix node name 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=u8yn4zhzp.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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