From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfc] Mark NEWS as documentation
Date: Fri, 31 Mar 2006 02:40:00 -0000 [thread overview]
Message-ID: <20060330152607.7f780acb@ironwood.lan> (raw)
In-Reply-To: <20060330172008.GK32409@nevyn.them.org>
On Thu, 30 Mar 2006 12:20:08 -0500
Daniel Jacobowitz <drow@false.org> wrote:
> This is something we discussed doing last year, before the MAINTAINERS
> changes, that I never came back to. Does everyone still agree with
> this change?
>
> --
> Daniel Jacobowitz
> CodeSourcery
>
> 2006-03-30 Daniel Jacobowitz <dan@codesourcery.com>
>
> * MAINTAINERS: Move NEWS to the documentation entry.
This is okay with me.
Kevin
next prev parent reply other threads:[~2006-03-30 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 22:26 Daniel Jacobowitz
2006-03-30 23:05 ` Mark Kettenis
2006-03-31 2:05 ` Jim Blandy
2006-03-31 2:40 ` Kevin Buettner [this message]
2006-05-05 23:20 ` 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=20060330152607.7f780acb@ironwood.lan \
--to=kevinb@redhat.com \
--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