From: Jim Blandy <jimb@red-bean.com>
To: gdb-patches@sourceware.org
Subject: Re: MAINTAINERS file updated with ping results
Date: Tue, 07 Feb 2006 19:01:00 -0000 [thread overview]
Message-ID: <8f2776cb0602071101t11fc941dqf840c6975b2c4cfd@mail.gmail.com> (raw)
In-Reply-To: <20060207154246.GA20262@nevyn.them.org>
If I'm reading the descriptions right, it's not meaningful to list
someone as both a global maintainer and as an authorized committer;
the former has the rights of the latter. But of the entries now in
"Authorized Committers", many belong to people who are also global
maintainers.
To be clear: I think it's very important that people are given credit
for their contributions; it's one of my primary motivations in working
on Free software. So if people feel that having their names listed in
both places is valuable in being recognized for their work, I don't
object. My point is that, as far as our procedures are concerned, it
seems redundant.
So if the general sense is that the first purpose of gdb/MAINTAINERS
is to describe our permissions and responsibilities, then it should be
trimmed.
next prev parent reply other threads:[~2006-02-07 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 15:42 Daniel Jacobowitz
2006-02-07 19:01 ` Jim Blandy [this message]
2006-02-07 19:15 ` 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=8f2776cb0602071101t11fc941dqf840c6975b2c4cfd@mail.gmail.com \
--to=jimb@red-bean.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