From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: carlton@math.stanford.edu
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] fnchange.lst
Date: Tue, 01 Oct 2002 11:33:00 -0000 [thread overview]
Message-ID: <6480-Tue01Oct2002213244+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <ro1elbbwcos.fsf@jackfruit.Stanford.EDU> (message from David Carlton on 30 Sep 2002 11:32:35 -0700)
> From: David Carlton <carlton@math.stanford.edu>
> Date: 30 Sep 2002 11:32:35 -0700
>
> On Sun, 29 Sep 2002 07:24:27 +0200 (IST), Eli Zaretskii <eliz@is.elta.co.il> said:
> > On 27 Sep 2002, David Carlton wrote:
>
> > This one is not needed; the gdb.c++ -> gdb.cxx transformation will
> > be performed automatically.
>
> I see; thanks for the info.
>
> Should I go through fnchange.lst and get rid of all the gdb.c++ ->
> gdb.cxx transformations except for the the first one (renaming the
> directory) and the m-static1.cc one that I added?
Oops, sorry. I see that I was wrong: all files in gdb.c++ directory
need to be explicitly renamed like you did in your original patch.
I'm terribly sorry for any inconvenience.
prev parent reply other threads:[~2002-10-01 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-27 12:23 David Carlton
2002-09-28 22:27 ` Eli Zaretskii
2002-09-30 11:32 ` David Carlton
2002-10-01 11:33 ` Eli Zaretskii [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=6480-Tue01Oct2002213244+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=carlton@math.stanford.edu \
--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