Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Improve help set/unset/show substitute-path
Date: Sat, 13 Jan 2007 14:11:00 -0000	[thread overview]
Message-ID: <u3b6fhv8h.fsf@gnu.org> (raw)
In-Reply-To: <20070113140320.GL537@adacore.com> (message from Joel Brobecker 	on Sat, 13 Jan 2007 18:03:20 +0400)

> Date: Sat, 13 Jan 2007 18:03:20 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> Thanks for the feedback, Eli. With your help, I think this second version
> is a huge improvement.
> 
> 2007-01-13  Joel Brobecker  <brobecker@adacore.com>
> 
>         * source.c (_initialize_source): Improve the help text of
>         the substitute-path commands.
> 
> Tested on x86-linux, no regression.
> OK to commit?

This version is fine with me, thanks.


  reply	other threads:[~2007-01-13 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  7:15 Joel Brobecker
2007-01-12 14:36 ` Eli Zaretskii
2007-01-13 14:02   ` Joel Brobecker
2007-01-13 14:11     ` Eli Zaretskii [this message]
2007-01-15  3:58       ` Joel Brobecker

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=u3b6fhv8h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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