From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Re: CML2-2.1.3 is available
Date: 22 Jan 2002 08:29:00 +0200 [thread overview]
Message-ID: <8HM4sDkXw-B@khms.westfalen.de> (raw)
In-Reply-To: <E16Snav-0001kl-00@starship.berlin>
In-Reply-To: <3C4C4A60.7030700@dplanet.ch> <20020115145324.A5772@thyrsus.com> <E16ShDP-0001ic-00@starship.berlin> <3C4C4A60.7030700@dplanet.ch> <E16Snav-0001kl-00@starship.berlin>
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:
> > Daniel Phillips wrote:
> >
> > >
> > > I detect a slight lack of symmetry here, shouldn't it be "make
> > > autoconfig"? Pardon me if this has been beaten to^W^W discussed above.
> >
> >
> > Yes. It should be "make autoconfig", for symmterty reasons :-)
> > I called the files and the project autoconfigure, because
> > 'autoconfig' is already an utility made by GNU. (not related
> > to kernel)
>
> 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.)
MfG Kai
next prev parent reply other threads:[~2002-01-22 7:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 19:53 CML2-2.1.3 is available Eric S. Raymond
2002-01-15 20:15 ` Nicolas Pitre
2002-01-15 20:18 ` Eric S. Raymond
2002-01-15 20:41 ` Nicolas Pitre
2002-01-15 19:19 ` Rob Landley
2002-01-16 3:48 ` Eric S. Raymond
2002-01-16 6:29 ` Peter Samuelson
2002-01-16 6:32 ` Eric S. Raymond
2002-01-16 7:13 ` Peter Samuelson
2002-01-16 6:36 ` Alexander Viro
2002-01-16 0:15 ` Henning P. Schmiedehausen
2002-01-15 20:16 ` Anton Altaparmakov
2002-01-15 20:24 ` Eric S. Raymond
2002-01-15 19:30 ` Rob Landley
2002-01-16 3:58 ` Eric S. Raymond
2002-01-15 20:25 ` Russell King
2002-01-15 19:37 ` Rob Landley
2002-01-17 1:18 ` Val Henson
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 [this message]
2002-01-23 21:45 ` Daniel Phillips
2002-01-16 0:38 ` Peter Samuelson
2002-01-15 20:26 ` Ross Vandegrift
2002-01-16 4:02 ` Eric S. Raymond
2002-01-16 16:38 ` Ross Vandegrift
2002-01-16 16:59 ` Ross Vandegrift
2002-01-16 18:29 ` Rob Landley
2002-01-18 18:32 ` Ross Vandegrift
2002-01-22 5:31 ` Eric S. Raymond
2002-01-15 20:27 ` Robert Love
2002-01-15 21:09 ` David Lang
2002-01-16 15:06 ` Horst von Brand
2002-01-16 21:31 ` Eric S. Raymond
2002-01-16 21:56 ` Horst von Brand
2002-01-16 21:47 ` Eric S. Raymond
2002-01-17 1:26 ` David Woodhouse
2002-01-17 1:43 ` Eric S. Raymond
2002-01-17 8:53 ` David Woodhouse
2002-01-17 13:37 ` Eric S. Raymond
2002-01-17 14:09 ` David Woodhouse
2002-01-17 14:29 ` Eric S. Raymond
2002-01-16 23:36 ` David Lang
2002-01-18 6:48 ` Kai Henningsen
[not found] <fa.i9jpu1v.8nmk39@ifi.uio.no>
[not found] ` <fa.hoedihv.1fn2r15@ifi.uio.no>
2002-01-22 9:11 ` [kbuild-devel] " Giacomo Catenazzi
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=8HM4sDkXw-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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