From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/13 v6] legal-info improvements and completeness (branch yem/legal-3)
Date: Fri, 6 May 2016 00:01:55 +0200 [thread overview]
Message-ID: <20160505220155.GD4367@free.fr> (raw)
In-Reply-To: <ef5ac802-80d2-e842-fb45-4a32aa0e3507@mind.be>
Arnout, All,
On 2016-05-04 00:33 +0200, Arnout Vandecappelle spake thusly:
> On 04/29/16 00:27, Yann E. MORIN wrote:
> >Hello All!
> >
> >This series brings improvements to the legal-info infrastructure, so
> >that we provide the most complete and correct content in the output of
> >legal-info.
> >
> >TL;DR:
> >
> >Currently, our legal-info ouput is missing two types of files that might
> >be important to have included in the legal-info output:
> > - patches
> > - extra downloads
> >
> >
> >This series is split in 5 consecutive parts, each depending on the
> >previous ones:
> >
> > - patches 1-4 make sure legal-info will work in off-line mode;
> >
> > - patches 5-7 reorganise the legal-info directory structure to
> > accomodate for the fact that more than one source archive/file may
> > be saved for each package;
> >
> > - patches 8-11 actually save the patches and extra downloads in the
> > legal-info output;
> >
> > - patch 12 adds a list of hashes for all files in the legal-info
> > output;
> >
> > - patch 15 (from Luca) explicits patches licensing.
>
> That's patch 13, actually :-)
Doh... Are you sure? ;-)
/me looks at his keyboard. '3' and '5' are not side-by-side; there is
'4' in-between... Damn, so far for my kbd-dislexia... ;-)
> For 2016.05, we certainly still want patch 13, and probably also patches 1,
> 2, 5, 6, 7, 8, 9, 11 (because they fix a real issue, that legal-info is
> incomplete). I do have some comments on these but it's nitpicking mostly.
>
> The other patches are more controversial.
As much as I can see that patch 4 (and 3) might be controversial, I fail
to see why patch 10 (bail-out when two patches are named the same) is
still controversial.
For that patch, I switched from renaming to bailing out after both
Thomas, Luca and you commented that was what you prefered.
I also stated that I had implemented both solutions, but posted the
renaming one so as to not break existing system. But surely, if I had
both solutions, it was for a reason: I also prefer bailing out. ;-)
So, I fail to see the controversy on that patch. ;-)
As for 12, Thomas and Luca already acked it...
> If you would repost, do you think you could take that order?
I doubt it...
I can try, but if I face a rebase hell, I'll bail out...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2016-05-05 22:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 22:27 [Buildroot] [PATCH 00/13 v6] legal-info improvements and completeness (branch yem/legal-3) Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 01/13 v6] support/scripts: add helper to hardlink-or-copy Yann E. MORIN
2016-05-03 22:53 ` Arnout Vandecappelle
2016-05-05 22:38 ` Yann E. MORIN
2016-05-07 18:44 ` Arnout Vandecappelle
2016-05-08 7:25 ` Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 02/13 v6] core/legal-info: use the helper to install source archives Yann E. MORIN
2016-05-03 22:57 ` Arnout Vandecappelle
2016-05-05 22:44 ` Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 03/13 v6] core/pkg-generic: reorder variables definitions for legal-info Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 04/13 v6] core/legal-info: ensure legal-info works in off-line mode Yann E. MORIN
2016-05-03 23:13 ` Arnout Vandecappelle
2016-04-28 22:27 ` [Buildroot] [PATCH 05/13 v6] core/pkg-generic: add variable to store the package rawname-version Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 06/13 v6] core/legal-info: install source archives in their own sub-dir Yann E. MORIN
2016-05-03 23:14 ` Arnout Vandecappelle
2016-05-05 22:55 ` Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 07/13 v6] core/legal-info: add package version to license directory Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 08/13 v6] core/apply-patches: store full path of applied patches Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 09/13 v6] core/legal-info: also save patches Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 10/13 v6] support/apply-patches: bail-out on duplicate patch basenames Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 11/13 v6] core/legal-info: also save extra downloads Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 12/13 v6] core/legal-info: generate a hash of all saved files Yann E. MORIN
2016-04-28 22:27 ` [Buildroot] [PATCH 13/13 v6] legal-info: explicitly state how patches are licensed Yann E. MORIN
2016-05-03 22:34 ` Arnout Vandecappelle
2016-05-03 22:33 ` [Buildroot] [PATCH 00/13 v6] legal-info improvements and completeness (branch yem/legal-3) Arnout Vandecappelle
2016-05-05 22:01 ` Yann E. MORIN [this message]
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=20160505220155.GD4367@free.fr \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.