From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Thomas Woerner <twoerner@redhat.com>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: Missing GPL headers
Date: Fri, 26 Feb 2010 16:06:43 +0100 [thread overview]
Message-ID: <4B87E383.4020804@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1002261154001.29558@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Friday 2010-02-26 11:42, Thomas Woerner wrote:
>
>> Hello,
>>
>> lots of files in the iptables tree are missing the GPL header but contain
>> copyright messages.
>
> I don't speak authoritatively, but the Linux kernel also has some files
> - usually those dating back to the initial years of Linux - that have no
> GPL header either, and everybody seems to be fine with that. See
> kernel/exit.c.
Yeah, the COPYING file states GPL-2, that applies to all files which
don't carry a seperate copyright statement.
prev parent reply other threads:[~2010-02-26 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 10:42 Missing GPL headers Thomas Woerner
2010-02-26 10:55 ` Jan Engelhardt
2010-02-26 15:06 ` Patrick McHardy [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=4B87E383.4020804@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=twoerner@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).