From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 00/22] Automatically produce legal compliance info
Date: Mon, 16 Jul 2012 17:55:24 +0200 [thread overview]
Message-ID: <20120716175524.4ecb6b99@skate> (raw)
In-Reply-To: <1337276001-26149-1-git-send-email-luca@lucaceresoli.net>
Le Thu, 17 May 2012 19:32:59 +0200,
Luca Ceresoli <luca@lucaceresoli.net> a ?crit :
> here is the third version of the legal-info feature implementation.
>
> Links to discussion of previous versions:
> v1:
> http://lists.busybox.net/pipermail/buildroot/2012-January/049590.html
> v2:
> http://lists.busybox.net/pipermail/buildroot/2012-March/051132.html
> v3: http://lists.busybox.net/pipermail/buildroot/2012-May/053574.html
>
> This version is only a minor update to fix various issues reported by
> other developers. There are not changes to the general structure, so
> please see the link above for v3 for a detailed presentation.
>
> Let me repeat only my plea to all Buildroot developers to read and
> give feedback on patch 9.
> It gives an advice from Buildroot developers to Buildroot users about
> how to comply with both Buildroot's and the packages' licenses.
> Of course this must match as much as possible what the developers
> think, so please read it and give either your different views or your
> ack (preferably with a formal Acked-by tag).
Ok, this series has been around for a while. I think that the overall
idea has been accepted by everybody, and has been discussed during the
Buildroot Developers Meeting in February.
Even though I think there might be a few possibilities to make the code
a bit nicer in patch 01/22, that's only internal implementation details
that can be improved at a later point.
Therefore, I'm now hesitating between those two solutions:
(1) Pulling all this in the current master, so that it will be part of
the next 2012.08 release. The chance of breaking seems fairly
limited to me, and this code has been around for a while, and I'd
like us to make progress on this.
(2) Be a bit safer, and wait the end of July to merge this into the
-next branch, once 2012.08-rc1 has been released.
What's the community opinion on this? At the moment, I'm leaning
towards (1), but I'd like to hear others opinion on this.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-16 15:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 17:32 [Buildroot] [PATCH v4 00/22] Automatically produce legal compliance info Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 01/22] legal-info: infrastructure to collect legally-relevant material Luca Ceresoli
2012-05-21 21:21 ` Arnout Vandecappelle
2012-05-17 17:33 ` [Buildroot] [PATCH v4 02/22] gettext: warn that legal-info is not implemented Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 03/22] netkitbase: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 04/22] netkittelnet: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 05/22] newt: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 06/22] ttcp: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 07/22] vpnc: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 08/22] manual: document usage of the legal-info feature Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 09/22] manual: add advice about GPL compliance for Buildroot Luca Ceresoli
2012-05-17 20:56 ` Thomas De Schampheleire
2012-05-20 12:37 ` Arnout Vandecappelle
2012-07-05 13:52 ` Luca Ceresoli
2012-07-05 20:23 ` Arnout Vandecappelle
2012-05-17 17:33 ` [Buildroot] [PATCH v4 10/22] linux: define license Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 11/22] m4: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 12/22] mpc: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 13/22] fakeroot: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 14/22] bzip2: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 15/22] directfb: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 16/22] iostat: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 17/22] lzo: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 18/22] lzop: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 19/22] libusb: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 20/22] pcre: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 21/22] netsnmp: " Luca Ceresoli
2012-05-17 17:33 ` [Buildroot] [PATCH v4 22/22] berkeleydb: " Luca Ceresoli
2012-06-20 13:07 ` [Buildroot] [PATCH v4 00/22] Automatically produce legal compliance info Luca Ceresoli
2012-07-16 15:55 ` Thomas Petazzoni [this message]
2012-07-17 14:55 ` Thomas De Schampheleire
2012-07-17 15:07 ` Maxime Ripard
2012-07-17 15:18 ` Samuel Martin
2012-07-17 17:36 ` Thomas Petazzoni
2012-07-17 18:58 ` Thomas Petazzoni
2012-07-19 10:11 ` Luca Ceresoli
2012-07-19 11:30 ` Thomas Petazzoni
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=20120716175524.4ecb6b99@skate \
--to=thomas.petazzoni@free-electrons.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