From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] arptables: bump to version 0.0.4
Date: Sat, 12 Jan 2013 09:16:39 -0300 [thread overview]
Message-ID: <50F15427.5030008@zacarias.com.ar> (raw)
In-Reply-To: <20130112131019.4ca0717b@skate>
On 01/12/2013 09:10 AM, Thomas Petazzoni wrote:
> Another option is to contact the authors and ask them to clarify the
> licensing? It's not like Rusty Russell is MIA :-)
Looking at extensions/arpt_CLASSIFY.c it specifies v2+ so i think it's
safe to assume this given that as you pointed out on IRC Debian also
classifies it so.
Patch forthcoming.
Regards.
next prev parent reply other threads:[~2013-01-12 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 11:37 [Buildroot] [PATCH 1/2] hiawatha: bump to version 8.7 Gustavo Zacarias
2013-01-12 11:37 ` [Buildroot] [PATCH 2/2] arptables: bump to version 0.0.4 Gustavo Zacarias
2013-01-12 11:58 ` Thomas Petazzoni
2013-01-12 12:07 ` Gustavo Zacarias
2013-01-12 12:10 ` Thomas Petazzoni
2013-01-12 12:16 ` Gustavo Zacarias [this message]
2013-01-12 20:09 ` [Buildroot] [PATCH 1/2] hiawatha: bump to version 8.7 Peter Korsgaard
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=50F15427.5030008@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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