From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-158326-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 13790 invoked by alias); 25 Nov 2009 22:26:26 -0000
Received: (qmail 13782 invoked by uid 22791); 25 Nov 2009 22:26:25 -0000
X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 	tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from c60.cesmail.net (HELO c60.cesmail.net) (216.154.195.49)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 25 Nov 2009 22:26:20 +0000
Received: from unknown (HELO epsilon2) ([192.168.1.60])   by c60.cesmail.net with ESMTP; 25 Nov 2009 17:26:18 -0500
Received: from 89.240.199.199 ([89.240.199.199]) by webmail.spamcop.net 	(Horde MIME library) with HTTP; Wed, 25 Nov 2009 17:26:18 -0500
Message-ID: <20091125172618.ydch3h9sg0ws44ko-nzlynne@webmail.spamcop.net>
Date: Wed, 25 Nov 2009 22:26:00 -0000
From: Joern Rennecke <amylaar@spamcop.net>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: trivial trailing whitespace issue
References: <alpine.LNX.2.00.0911251737500.17161@zhemvz.fhfr.qr> 	<alpine.LNX.2.00.0911251739340.17161@zhemvz.fhfr.qr> 	<10911251651.AA00241@vlsi1.ultra.nyu.edu> <4B0D6245.3010601@redhat.com> 	<Pine.LNX.4.64.0911251803590.15566@wotan.suse.de> 	<4B0D6708.7060306@redhat.com> 	<Pine.LNX.4.64.0911251722260.21848@digraph.polyomino.org.uk> 	<4B0D6DE6.4010708@gmail.com> 	<alpine.LNX.2.00.0911252032380.17161@zhemvz.fhfr.qr> 	<4B0D8C4B.9020405@redhat.com> <4B0D8ED5.1060303@starynkevitch.net> 	<Pine.LNX.4.64.0911252053250.31853@digraph.polyomino.org.uk> 	<4B0DA40A.1090205@starynkevitch.net>
In-Reply-To: <4B0DA40A.1090205@starynkevitch.net>
MIME-Version: 1.0
Content-Type: text/plain; 	charset=UTF-8; 	DelSp="Yes"; 	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
X-SW-Source: 2009-11/txt/msg00726.txt.bz2

Quoting Basile STARYNKEVITCH <basile@starynkevitch.net>:
> I would imagine that patching GNU indent (in its source code form)
> requires a copyright assignment specific to it (and uncovered by a, or
> at least "mine", GCC copyright assigment to FSF). If this is the case,
> I [Basile] won't do it (because getting a copyright assignemnt is so
> painful to me).

If you put a patch against GNU indent in contrib to format GCC-style,
wouldn't that then be a part of GCC and thus covered?

If that is the case, then you can post afterwards this piece of FSF-owned
GCC code to the indent maintainers...