From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] License for patches
Date: Wed, 24 Aug 2011 12:05:22 -0400 [thread overview]
Message-ID: <201108241205.23310.vapier@gentoo.org> (raw)
In-Reply-To: <4E5517E0.30003@finalbit.de>
On Wednesday, August 24, 2011 11:25:20 Lars Reemts wrote:
> Which license is relevant for the package specific patches distributed
> by buildroot? Formally it must be the GPL.
says who ? i dont see the logic here.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110824/5fd8df2f/attachment.asc>
next prev parent reply other threads:[~2011-08-24 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 15:25 [Buildroot] License for patches Lars Reemts
2011-08-24 16:05 ` Mike Frysinger [this message]
2011-08-24 16:14 ` Grant Edwards
2011-08-24 16:55 ` Yann E. MORIN
2011-08-24 20:48 ` Peter Korsgaard
2011-08-24 17:13 ` Mike Frysinger
2011-08-24 17:38 ` Grant Edwards
2011-08-24 18:08 ` Mike Frysinger
2011-08-24 20:47 ` Peter Korsgaard
2011-08-29 12:32 ` Thomas Petazzoni
2011-08-24 16:21 ` Robin Holt
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=201108241205.23310.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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