Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Jim Ingham <jingham@apple.com>, gdb-patches@sources.redhat.com
Subject: Re: complete command doesn't work for files...
Date: Sat, 27 Sep 2003 04:36:00 -0000	[thread overview]
Message-ID: <vt2he2yrgul.fsf@zenia.home> (raw)
In-Reply-To: <3F7344EF.30407@redhat.com>


Andrew Cagney <ac131313@redhat.com> writes:
> why apparently simpler alternative techniques don't work.

Right --- this is an example of a boundary case, where a comment that
helps one understand the justification for the present code resembles
a historical comment, that would belong in a ChangeLog.


  reply	other threads:[~2003-09-27  4:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 23:14 Jim Ingham
2003-09-24 23:25 ` Joel Brobecker
2003-09-24 23:30   ` Andrew Cagney
2003-09-25 19:04     ` Jim Ingham
2003-09-25 19:41       ` Andrew Cagney
2003-09-27  4:36         ` Jim Blandy [this message]
2004-01-19 16:22 ` Daniel Jacobowitz
2004-01-20 22:19   ` Jim Ingham
2004-02-01  5:51     ` Daniel Jacobowitz

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=vt2he2yrgul.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jingham@apple.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