From: Joe Buck <jbuck@synopsys.com>
To: Richard Stallman <rms@gnu.org>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>, gcc@gcc.gnu.org
Subject: Re: Manual contributions and copyright assignments
Date: Fri, 23 May 2003 17:42:00 -0000 [thread overview]
Message-ID: <20030523103648.A25849@synopsys.com> (raw)
In-Reply-To: <E19IlWH-0006ve-Gh@fencepost.gnu.org>; from rms@gnu.org on Thu, May 22, 2003 at 04:33:49AM -0400
On Thu, May 22, 2003 at 04:33:49AM -0400, Richard Stallman wrote:
> I am worried about the idea that all 100 people with write access can
> install others' changes. That means we depend on all 100 of them to
> check properly for legal papers. It is unreliable to have 100 people
> doing this!
Don't worry; only a very small number of people have global write privilege.
The others only have permission to modify very limited areas of the compiler,
or to check in a patch that has been approved by someone with greater privilege.
Generally speaking, these people are checking in their own patches, and
all have papers on file.
> I have no objection to your allowing 100 people to install their own
> changes--if you trust them, that's good enough for me. But unless you
> have very effective procedures for making sure all 100 people check
> papers properly, you should greatly reduce the people who are allowed
> to install changes other than their own.
That's pretty much the process we follow; when an unknown person submits
a patch, the very first question asked has to do with the status of their
papers.
next prev parent reply other threads:[~2003-05-23 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 12:02 Gerald Pfeifer
2003-05-22 11:44 ` Richard Stallman
2003-05-23 17:42 ` Joe Buck [this message]
2003-05-23 18:22 Nathanael Nerode
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=20030523103648.A25849@synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=rms@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).