From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] openzwave: new package
Date: Mon, 25 Apr 2016 14:44:09 +0200 [thread overview]
Message-ID: <87wpnlq2na.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160425092535.3c606c2a@free-electrons.com> (Thomas Petazzoni's message of "Mon, 25 Apr 2016 09:25:35 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> I am not sure how much strict we (the Buildroot community) want to be
> regarding such confidentiality footers. After all, it only says "may
> contain confidential or privileged information", which means that it
> may also contain public information. I'm not sure what other
> open-source projects are doing? Apparently at
> http://lists.infradead.org/pipermail/linux-mtd/2013-December/050573.html,
> the Linux MTD maintainer rejected a patch due to a confidentiality
> footer.
> Peter, Arnout, Yann, what's your position on this?
IANAL, but personally I find the disclaimers ugly/noisy to look at but
not bad enough to reject patches for it.
> (http://www.economist.com/node/18529895 is an interesting article on
> the matter, probably useful to share with the relevant folks in
> Orange :-))
Yeah, indeed.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-04-25 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 14:20 [Buildroot] [PATCH 1/1] openzwave: new package fabrice.fontaine at orange.com
2016-04-22 22:39 ` Thomas Petazzoni
[not found] ` <4485_1461568414_571DC39E_4485_77_1_EEB3FED4859B6C488DDDEC4B2D3DE92B0FC5BBD4@OPEXCLILM23.corporate.adroot.infra.ftgroup>
2016-04-25 7:25 ` Thomas Petazzoni
2016-04-25 12:44 ` Peter Korsgaard [this message]
2016-04-25 14:31 ` fabrice.fontaine at orange.com
-- strict thread matches above, loose matches on Subject: below --
2016-04-22 13:37 fabrice.fontaine at orange.com
2016-04-20 13:38 Joris Lijssens
2016-04-21 14:12 ` Julien Boibessot
2016-04-22 9:56 ` Joris Lijssens
2016-03-04 15:15 fabrice.fontaine at orange.com
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=87wpnlq2na.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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