From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot and GPL compliance
Date: Mon, 19 Dec 2011 22:08:37 +0100 [thread overview]
Message-ID: <4EEFA7D5.8060709@lucaceresoli.net> (raw)
In-Reply-To: <4EEDDD2D.1030801@relinux.de>
Hi Stephan,
Stephan Hoffmann wrote:
>> Technically, the only solution I see is to add 'prominent notices' to
>> modified files in our own repository, but manually remove them when
>> submitting patches to the buildroot list. This is annoying but may be
>> the only legal possibility. How do others see this?
> I think we should try to find out how other projects handle this or how
> lawyers or GNU comment on this.
Sounds like a good idea. I think the FSF provides free (as in beer)
consultancy to free (as in speech) software projects of some importance.
It might be worth trying, after we have focused on a few precise
questions.
Luca
next prev parent reply other threads:[~2011-12-19 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 7:40 [Buildroot] Buildroot and GPL compliance Thomas De Schampheleire
2011-12-18 12:31 ` Stephan Hoffmann
2011-12-19 21:08 ` Luca Ceresoli [this message]
2011-12-19 21:02 ` Luca Ceresoli
2012-01-06 7:10 ` Mike Frysinger
2012-01-06 14:25 ` Michael S. Zick
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=4EEFA7D5.8060709@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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