From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA/NEWS] document addition of set/show/unset substitute-path
Date: Wed, 09 Aug 2006 03:19:00 -0000 [thread overview]
Message-ID: <20060808232646.GA3916@nevyn.them.org> (raw)
Message-ID: <20060809031900.9cagrStx3o5XMs7JojLey9ZJgdQnzCeWw4IOhF4BOao@z> (raw)
In-Reply-To: <20060808224119.GE19846@adacore.com>
On Tue, Aug 08, 2006 at 03:41:19PM -0700, Joel Brobecker wrote:
> Hello,
>
> What do you guys think of the following patch. I tried to keep
> things relatively short and succint. Does it need to be expanded
> a bit or is it clear enough?
>
> 2006-08-08 Joel Brobecker <brobecker@adacore.com>
>
> * NEWS: Add entry for new substitute-path commands.
>
> OK?
I'll wait for Eli's review, of course, but I think this is about right.
You rarely need to expand more than this in NEWS - just enough to
intrigue someone upgrading, and then let the manual do the rest.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-08 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 22:41 Joel Brobecker
2006-08-08 23:26 ` Daniel Jacobowitz [this message]
2006-08-09 3:19 ` Daniel Jacobowitz
2006-08-09 16:50 ` Eli Zaretskii
2006-08-09 16:51 ` 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=20060808232646.GA3916@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.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