From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23698 invoked by alias); 26 Apr 2010 15:11:35 -0000 Received: (qmail 23604 invoked by uid 22791); 26 Apr 2010 15:11:31 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Apr 2010 15:11:27 +0000 Received: from ams by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1O6Py0-0006q0-PW; Mon, 26 Apr 2010 11:11:24 -0400 From: "Alfred M. Szmidt" To: Mark Mielke CC: basile@starynkevitch.net, gcc@gcc.gnu.org, lopezibanez@gmail.com In-reply-to: <4BD49959.5070500@mark.mielke.cc> (message from Mark Mielke on Sun, 25 Apr 2010 15:34:49 -0400) Subject: Re: Why not contribute? (to GCC) Reply-to: ams@gnu.org References: <4BD20EDF.2050102@starynkevitch.net> <4BD49959.5070500@mark.mielke.cc> Message-Id: Date: Mon, 26 Apr 2010 15:11:00 -0000 X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-04/txt/msg00825.txt.bz2 Wouldn't contributing a patch to be read by the person who will be solving the problem, but without transferring of rights, introduce risk or liability for the FSF and GCC? That risk always exists; some level of trust has to exist somewhere.