From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 00/22] Automatically produce legal compliance info
Date: Tue, 17 Jul 2012 20:58:03 +0200 [thread overview]
Message-ID: <20120717205803.1dca9f8c@skate> (raw)
In-Reply-To: <20120717193610.638fabb2@skate>
Le Tue, 17 Jul 2012 19:36:10 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
> Following the comments of several Buildroot contributors, I have merged
> the 22 patches of your series. Thanks a lot for your perseverance in
> getting this merged!
I have also added the execution of 'make legal-info' to my autobuilder.
So all builds coming from the Free Electrons build server visible at
http://autobuild.buildroot.org will have the CSV file of the licenses.
It is not directly visible in the webpage, but if you go in the "dir"
link, and then look at the licenses-manifest.csv file, it corresponds
to the output/legal-info/manifest.csv file.
Example:
http://autobuild.buildroot.org/results/a07c8611de688b6dccbfae00ff153ad89f3e7f77/licenses-manifest.csv
This way, the legal-info machinery will be exercised on many packages.
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-17 18:58 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
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 [this message]
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=20120717205803.1dca9f8c@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