public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: cate@dplanet.ch
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Announce: Kernel Build for 2.5, Release 1 is available.
Date: Wed, 8 Aug 2001 13:54:58 +0200	[thread overview]
Message-ID: <20010808135457.A13261@caldera.de> (raw)
In-Reply-To: <200108081139.f78BdTH11980@ns.caldera.de> <3B712706.A7D566F1@math.ethz.ch>
In-Reply-To: <3B712706.A7D566F1@math.ethz.ch>; from cate@math.ethz.ch on Wed, Aug 08, 2001 at 01:48:22PM +0200

On Wed, Aug 08, 2001 at 01:48:22PM +0200, Giacomo Catenazzi wrote:
> Christoph Hellwig wrote:
> > 
> > In article <3B712392.A7CFEEC9@math.ethz.ch> you wrote:
> > > BTW we cannot ship the generated file without the source files,
> > > because of GPL.
> > 
> > That's wrong.
> 
> Why?
> 
> (Yes legally is wrong, and we should check case per case, but as far
> as we can do, we should GPL as much code as possible, and we should
> follow where possible the GPL also on non GPL code)

That's blurb.  You can just put the GPLed sources for the shipped
stuff somewhere else on kernel.org and you're fine.  There is no
fsckin need to have them in the same archive.

	Christoph

-- 
Whip me.  Beat me.  Make me maintain AIX.

  reply	other threads:[~2001-08-08 11:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08  6:58 Announce: Kernel Build for 2.5, Release 1 is available Keith Owens
2001-08-08  7:38 ` john slee
2001-08-08 11:07   ` Keith Owens
2001-08-08 11:33 ` [kbuild-devel] " Giacomo Catenazzi
2001-08-08 11:39   ` Christoph Hellwig
2001-08-08 11:48     ` Giacomo Catenazzi
2001-08-08 11:54       ` Christoph Hellwig [this message]
2001-08-08 12:06         ` Giacomo Catenazzi
2001-08-08 12:00       ` Andy Walker
2001-08-08 11:50   ` Keith Owens
2001-08-08 11:56     ` Alan Cox

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=20010808135457.A13261@caldera.de \
    --to=hch@ns.caldera.de \
    --cc=cate@dplanet.ch \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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