From: Massimiliano Hofer <max@nucleus.it>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: "Stephane Ouellette" <ouellettes@videotron.ca>,
"Eicke Friedrich/Klaus Degner" <ipp2p@ipp2p.org>,
"Sebastian Claßen" <sebastian.classen@freenet.ag>,
netfilter@vger.kernel.org,
"Andrew Schulman" <andrex@alumni.utexas.net>
Subject: Re: xtables-addons license (was: patch-o-matic problems..?)
Date: Wed, 30 Jul 2008 15:25:54 +0200 [thread overview]
Message-ID: <200807301525.55917.max@nucleus.it> (raw)
In-Reply-To: <alpine.LNX.1.10.0807271419120.9173@fbirervta.pbzchgretzou.qr>
On Sunday 27 July 2008, Jan Engelhardt wrote:
> >But there's a problem: there's no overall license file, and a lot of
> >the source files don't have license statements in them. Here are the
> >source files I find with no license:
> >
> >extensions/libxt_condition.c
>
> (Stephane and Massimiliano)
No problem for me. I agree on the GPLv2 for my code.
I just supposed it was implicit, since my code is tied to a GPLv2 project.
--
Bye,
Massimiliano Hofer
Nucleus
next prev parent reply other threads:[~2008-07-30 13:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 21:45 patch-o-matic problems..? Zoe Parsons
2008-07-20 9:09 ` Jan Engelhardt
2008-07-20 14:48 ` Zoe Parsons
2008-07-20 15:06 ` Jan Engelhardt
2008-07-23 0:36 ` Dave
2008-07-23 9:31 ` Jan Engelhardt
2008-07-25 10:01 ` xtables-addons license (was: patch-o-matic problems..?) Andrew Schulman
2008-07-27 20:35 ` Jan Engelhardt
2008-07-28 6:06 ` Sebastian Claßen
2008-07-28 13:47 ` Andrew Schulman
2008-07-30 13:25 ` Massimiliano Hofer [this message]
2008-07-30 13:36 ` Jan Engelhardt
2008-08-01 15:34 ` Massimiliano Hofer
2008-08-01 18:00 ` Jan Engelhardt
2008-08-01 19:08 ` Massimiliano Hofer
2008-08-10 14:09 ` Jan Engelhardt
2008-07-23 11:56 ` patch-o-matic problems..? Pablo Neira Ayuso
2008-07-23 12:05 ` Amos Jeffries
2008-07-23 13:04 ` Pablo Neira Ayuso
2008-07-23 10:12 ` Pablo Neira Ayuso
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=200807301525.55917.max@nucleus.it \
--to=max@nucleus.it \
--cc=andrex@alumni.utexas.net \
--cc=ipp2p@ipp2p.org \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.org \
--cc=ouellettes@videotron.ca \
--cc=sebastian.classen@freenet.ag \
/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