From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb@sourceware.org
Subject: Re: Maintainer policy for GDB - take N
Date: Tue, 17 Jan 2006 23:28:00 -0000 [thread overview]
Message-ID: <200601172208.k0HM8VBs014346@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060117212833.GA13230@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 17 Jan 2006 16:28:33 -0500)
> Date: Tue, 17 Jan 2006 16:28:33 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> On Fri, Jan 06, 2006 at 02:40:07PM -0500, Daniel Jacobowitz wrote:
> > Replacement text for MAINTAINERS:
>
> There was some dissatisfaction with my Overview :-) Is this any
> better? The only changes from the last posting are in the Overview,
> above the section heading for the Obvious Fix Rule, but it doesn't lend
> itself to diff well.
I like it; I think it's much clearer.
Thanks for doing this,
Mark
next prev parent reply other threads:[~2006-01-17 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 19:40 Daniel Jacobowitz
2006-01-06 23:15 ` Eli Zaretskii
2006-01-08 17:52 ` Mark Kettenis
2006-01-09 5:53 ` Jim Blandy
2006-01-09 18:00 ` Christopher Faylor
2006-01-17 22:09 ` Daniel Jacobowitz
2006-01-17 23:28 ` Mark Kettenis [this message]
2006-01-18 11:17 ` Christopher Faylor
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=200601172208.k0HM8VBs014346@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb@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