From: Olaf Titz <olaf@bigred.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: CIPE vs. GPLONLY_
Date: Sat, 12 Jan 2002 12:37:05 +0100 [thread overview]
Message-ID: <E16PMTC-0000af-00@bigred.inka.de> (raw)
In-Reply-To: <20020112010317.GA1765@top.worldcontrol.com> <E16PD12-0000wY-00@the-village.bc.nu>
> Add
>
> MODULE_LICENSE("GPL");
>
> to the cipe code and all will be well
That's already fixed in the CIPE CVS tree.
Olaf
prev parent reply other threads:[~2002-01-12 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 1:03 CIPE vs. GPLONLY_ brian
2002-01-12 1:31 ` Alan Cox
2002-01-12 1:48 ` brian
2002-01-12 3:26 ` Arnaldo Carvalho de Melo
2002-01-12 4:57 ` brian
2002-01-12 11:37 ` Olaf Titz [this message]
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=E16PMTC-0000af-00@bigred.inka.de \
--to=olaf@bigred.inka.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