public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Roger Sayle <roger@www.eyesopen.com>
Cc: gcc-patches@gcc.gnu.org, Jeffrey A Law <law@redhat.com>,
	Janis Johnson <janis187@us.ibm.com>, Mike Stump <mrs@apple.com>,
	David Edelsohn <dje@watson.ibm.com>,
	Loren James Rittle <rittle@labs.mot.com>,
	Andreas Jaeger <aj@suse.de>,
	"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
	gcc@gcc.gnu.org
Subject: Re: [PATCH] Duplicate entries in contrib.texi
Date: Thu, 03 Apr 2003 20:21:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.53.0304032107560.88500@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <Pine.LNX.4.44.0303290700290.12268-100000@www.eyesopen.com>

On Sat, 29 Mar 2003, Roger Sayle wrote:
> Reading through the entries in contrib.texi I've come across a
> strange discrepancy that several names are listed twice.  The
> problem is that we have two sections one for "contributors" and
> a second category for "testers".
>
> 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.

I pondered about this quite a bit now, and in fact the current state
is even more broken: we would need to acknowledge nearly _all_ of
those listed in the first section for testing as well.

This hardly makes sense, nor does keeping two lists where one is a subset
of the other. So I'd like to follow a somewhat different route along what
Janis suggested:

| We can remove people from "testers" if they are already listed above
| without adding "and testing" to their entries.

Namely,

 1) remove duplicate entries from the second section,
 2) add a general note concerning testing before the beginning of the
    first section, and
 3) specifically acknowledge those contributors who contributed more than
    an "average" amount of testing.

Those coming into my mind here (and that are not listed yet) include

 David Edelsohn for "ensuring GCC properly keeps working on AIX".
 Kaveh Ghazi for "continously testing GCC on a plethora of platforms".
 Andreas Jäger for "operating SPEC performance testers".
 Loren J. Rittle for "ensuring GCC properly keeps working on FreeBSD".

though
> However there are also glaring omissions from the testing section; Geoff
> Keating, Andreas Jaeger, Janis Johnson, Phil Edwards and Diego Novillo
> (who isn't even listed at all!) are big names in manual and automated

Geoff and Janis are already acknowledged, Andreas is in my list above,
and Diego I have already contacted concerning an entry.

Gerald

PS: Jeff, as the original maintainer of these lists, what's your
suggestion?

      parent reply	other threads:[~2003-04-03 19:26 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
2003-03-31 21:44 ` Janis Johnson
2003-04-03 20:21 ` Gerald Pfeifer [this message]

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=Pine.BSF.4.53.0304032107560.88500@naos.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=aj@suse.de \
    --cc=dje@watson.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    --cc=janis187@us.ibm.com \
    --cc=law@redhat.com \
    --cc=mrs@apple.com \
    --cc=rittle@labs.mot.com \
    --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).