From: Mike Stump <mrs@apple.com>
To: Roger Sayle <roger@www.eyesopen.com>
Cc: gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: [PATCH] Duplicate entries in contrib.texi
Date: Mon, 31 Mar 2003 18:47:00 -0000 [thread overview]
Message-ID: <6364154C-63A4-11D7-B09F-003065A77310@apple.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0303290700290.12268-100000@www.eyesopen.com>
On Saturday, March 29, 2003, at 06:55 AM, Roger Sayle wrote:
> Reading through the entries in contrib.texi I've come across a
> strange discrepancy that several names are listed twice.
> This has led to Joe Buck, Craig Burley, Ulrich Drepper, David
> Edelsohn, Kaveh Ghazi, Kate Hedstrom, Richard Henderson, Manfred
> Hollstein, Kamil Iskra, Jeff Law, Robert Lipe, Dave Love, H.J Lu,
> Mumit Khan, David Miller, Toon Moene, Alexandre Oliva, Loren J.
> Rittle, Peter Schmid, Franz Sirl, Mike Stump and Carlo Wood
> being listed twice.
As one of the named, I certainly don't have any problem with the patch.
It makes sense to group the contributions of individuals together into
one entry.
next prev parent reply other threads:[~2003-03-31 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 19:48 Roger Sayle
2003-03-31 18:47 ` Mike Stump [this message]
2003-03-31 21:44 ` Janis Johnson
2003-04-03 20:21 ` Gerald Pfeifer
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=6364154C-63A4-11D7-B09F-003065A77310@apple.com \
--to=mrs@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=roger@www.eyesopen.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).