From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: openembedded-core@lists.openembedded.org
Cc: Alexandre BELLONI <alexandre.belloni@bootlin.com>,
Khem Raj <raj.khem@gmail.com>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: [PATCH 0/2 v2] recipes-core/busybox: fixup licensing information (branch yem/busybox-licensing)
Date: Wed, 28 Oct 2020 16:47:53 +0100 [thread overview]
Message-ID: <cover.1603900066.git.yann.morin.1998@free.fr> (raw)
Hello All!
This small series adds a new common license, bzip2-1.0.4, to be used to
fix busybox' licensing information.
Changes v1 -> v2;
- add bzip2-1.0.4 to the common-licenses (Khem)
Regards,
Yann E. MORIN.
----------------------------------------------------------------
Yann E. MORIN (2):
common-licenses: add bzip2-1.0.4
recipes-core/busybox: fixup licensing information
meta/files/common-licenses/bzip2-1.0.4 | 43 ++++++++++++++++++++++++++++++++++
meta/recipes-core/busybox/busybox.inc | 7 +++---
2 files changed, 47 insertions(+), 3 deletions(-)
create mode 100644 meta/files/common-licenses/bzip2-1.0.4
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2020-10-28 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 15:47 Yann E. MORIN [this message]
2020-10-28 15:47 ` [PATCH 1/2 v2] common-licenses: add bzip2-1.0.4 Yann E. MORIN
2020-10-28 15:47 ` [PATCH 2/2 v2] recipes-core/busybox: fixup licensing information Yann E. MORIN
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=cover.1603900066.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
/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