Message-ID: <3C4D2CAE.5000702@debian.org>
Date: Tue, 22 Jan 2002 10:11:10 +0100
From: Giacomo Catenazzi <cate@debian.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Re: CML2-2.1.3 is available
In-Reply-To: <fa.i9jpu1v.8nmk39@ifi.uio.no> <fa.hoedihv.1fn2r15@ifi.uio.no>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org


Kai Henningsen wrote:

> phillips@bonn-fries.net (Daniel Phillips)  wrote on 22.01.02 in <E16Snav-0001kl-00@starship.berlin>:
>>On January 21, 2002 06:05 pm, Giacomo Catenazzi wrote:
>>
>>This is kernel autoconfig, different namespace, same idea.  I don't think
>>you have a problem.  Besides, last time I checked, autoconfig wasn't
>>copyrighted.
>>
> 
> Last time I checked, autoconf (not -ig) was GPL. But as long as you don't  
> use code from it, copyright is completely irrelevant anyway: trademark  
> status might be relevant when you're talking about names. (And %@$&$!  
> patent status when talking about algorithms.)
> 

No problem on copyright, licences,...
I choose (for the file names, not for the 'make autoconfig') a
longer name, to distinguish the kernel autoconfig from the
GNU autoconf (without the final 'ig').
Only for pratical reasons.

If autoconfigure will go in the kernel, I have not problems on
filenames, but when I initially created it, I thinked ev. to
distribuite it as a package. Here the name matter.

IMHO longer filename ia a good things (iff normal user should
not type it).

	giacomo

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/