From: Roland Hieber <rhi@pengutronix.de>
To: Christian Hermann <christian.hermann@hytera.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 03/13] procps: fix license identifier
Date: Mon, 22 Jul 2019 11:45:25 +0200 [thread overview]
Message-ID: <20190722094525.n7kf2g47w4qgmoys@pengutronix.de> (raw)
In-Reply-To: <20190719121803.28963-3-christian.hermann@hytera.de>
Reviewed-by: Roland Hieber <rhi@pengutronix.de>
If you're going to send v2 of the series, please put a short sentence in
the commit message with a more verbose justification, like:
All files contain the "or (at your option) any later version"
clause of the GPL-2.0 or the LGPL-2.1 dedication.
- Roland
On Fri, Jul 19, 2019 at 02:17:53PM +0200, Christian Hermann wrote:
> Signed-off-by: Christian Hermann <christian.hermann@hytera.de>
> ---
> rules/procps.make | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/rules/procps.make b/rules/procps.make
> index 8d19e7b4a..9a042900d 100644
> --- a/rules/procps.make
> +++ b/rules/procps.make
> @@ -24,7 +24,7 @@ PROCPS_SUFFIX := tar.xz
> PROCPS_URL := $(call ptx/mirror, SF, procps-ng/Production/$(PROCPS).$(PROCPS_SUFFIX))
> PROCPS_SOURCE := $(SRCDIR)/$(PROCPS).$(PROCPS_SUFFIX)
> PROCPS_DIR := $(BUILDDIR)/$(PROCPS)
> -PROCPS_LICENSE := GPL-2.0-only AND LGPL-2.0-only
> +PROCPS_LICENSE := GPL-2.0-or-later AND LGPL-2.1-or-later
> PROCPS_LICENSE_FILES := \
> file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> file://COPYING.LIB;md5=4cf66a4984120007c9881cc871cf49db
> --
> 2.22.0
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Roland Hieber | r.hieber@pengutronix.de |
Pengutronix e.K. | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-07-22 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 12:17 [ptxdist] [PATCH 01/13] polkit: add " Christian Hermann
2019-07-19 12:17 ` [ptxdist] [PATCH 02/13] portmap: " Christian Hermann
2019-07-22 9:37 ` Roland Hieber
2019-07-19 12:17 ` [ptxdist] [PATCH 03/13] procps: fix " Christian Hermann
2019-07-22 9:45 ` Roland Hieber [this message]
2019-07-19 12:17 ` [ptxdist] [PATCH 04/13] bash: " Christian Hermann
2019-07-22 10:10 ` Roland Hieber
2019-07-19 12:17 ` [ptxdist] [PATCH 05/13] bc: " Christian Hermann
2019-07-22 10:16 ` Roland Hieber
2019-07-19 12:17 ` [ptxdist] [PATCH 06/13] cifs-utils: " Christian Hermann
2019-07-19 12:17 ` [ptxdist] [PATCH 07/13] ddrescue: " Christian Hermann
2019-07-19 12:17 ` [ptxdist] [PATCH 08/13] diffutils: " Christian Hermann
2019-07-19 12:17 ` [ptxdist] [PATCH 09/13] fuse: fix license identifier (split) Christian Hermann
2019-07-19 12:18 ` [ptxdist] [PATCH 10/13] dosfstools: fix license identifier Christian Hermann
2019-07-19 12:18 ` [ptxdist] [PATCH 11/13] file: " Christian Hermann
2019-07-19 12:18 ` [ptxdist] [PATCH 12/13] dnsmasq: add " Christian Hermann
2019-07-19 12:18 ` [ptxdist] [PATCH 13/13] findutils: " Christian Hermann
2019-07-22 9:49 ` [ptxdist] [PATCH 01/13] polkit: " Roland Hieber
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=20190722094525.n7kf2g47w4qgmoys@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=christian.hermann@hytera.de \
--cc=ptxdist@pengutronix.de \
/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