From: Giacomo Catenazzi <cate@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Re: CML2-2.1.3 is available
Date: Tue, 22 Jan 2002 10:11:10 +0100 [thread overview]
Message-ID: <3C4D2CAE.5000702@debian.org> (raw)
In-Reply-To: <fa.i9jpu1v.8nmk39@ifi.uio.no> <fa.hoedihv.1fn2r15@ifi.uio.no>
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
next parent reply other threads:[~2002-01-22 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.i9jpu1v.8nmk39@ifi.uio.no>
[not found] ` <fa.hoedihv.1fn2r15@ifi.uio.no>
2002-01-22 9:11 ` Giacomo Catenazzi [this message]
2002-01-22 9:20 ` CML2-2.1.3 is available Keith Owens
2002-01-15 19:53 Eric S. Raymond
2002-01-15 20:25 ` Russell King
2002-01-15 19:37 ` Rob Landley
2002-01-21 16:22 ` Daniel Phillips
2002-01-21 17:05 ` [kbuild-devel] " Giacomo Catenazzi
2002-01-21 23:11 ` Daniel Phillips
2002-01-22 6:29 ` Kai Henningsen
2002-01-23 21:45 ` Daniel Phillips
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=3C4D2CAE.5000702@debian.org \
--to=cate@debian.org \
--cc=linux-kernel@vger.kernel.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