From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: kevinb@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] More file-name related fixes
Date: Wed, 02 May 2001 14:08:00 -0000 [thread overview]
Message-ID: <1190-Thu03May2001000950+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <1010502202816.ZM3883@ocotillo.lan>
> Date: Wed, 2 May 2001 13:28:16 -0700
> From: Kevin Buettner <kevinb@cygnus.com>
>
> On May 2, 8:26pm, Eli Zaretskii wrote:
>
> > +#if 0
> > +
> > static struct sym_and_file {
> > char *sym;
> > char *file;
> > @@ -3352,6 +3340,8 @@ make_file_symbol_completion_list (char *
> > return (return_val);
> > }
> >
> > +#endif
> > +
>
> Is there any reason for leaving the code disabled by the #if 0
> in place?
As I wrote in a follow-up, this hunk should be disregarded. It
doesn't belong to this change (I was experimenting with something when
I ran Diff), and got into my message through my own negligence.
Sorry.
Thanks for reviewing the patch.
next prev parent reply other threads:[~2001-05-02 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 10:26 Eli Zaretskii
2001-05-02 13:28 ` Kevin Buettner
2001-05-02 14:08 ` Eli Zaretskii [this message]
2001-05-03 21:00 ` Elena Zannoni
2001-05-05 23:07 ` 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=1190-Thu03May2001000950+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@cygnus.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