Automatically produce legal compliance info
Get series with b4
b4 am [email protected]Versions newest first
- v4 Latest0 of 22 patches 0 repliesNew
Patches in v4 No applies recorded yet
None of the 22 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.
Cover letter [Buildroot] [PATCH v4 00/22] Automatically produce legal compliance info
Le 17/07/2012 16:55, Thomas De Schampheleire a ?crit :
Quoted 45 lines
Op 16 jul. 2012 09:55 schreef "Thomas Petazzoni" < thomas.petazzoni at free-electrons.com> het volgende:
Quoted 43 lines
Le Thu, 17 May 2012 19:32:59 +0200,
Luca Ceresoli <[email protected]> a ?crit :Quoted 13 lines
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.htmlThis 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.
Quoted 7 lines
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.
Quoted 6 lines
Quoted 2 lines
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.
I'd go for (1). As you say, chances of breaking something is small. Plus, if we can get this into the August release, we'll start getting further feedback right away instead of waiting another three months.
Agreed.
I'd go for (1) too.
Maxime
Signature · 4 lines
Maxime Ripard, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com