From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] doc: Files are added to <PKG>_LICENSE_FILES
Date: Wed, 8 Feb 2023 12:49:43 +0100 [thread overview]
Message-ID: <20230208114943.2009054-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230119162132.133854-1-u.kleine-koenig@pengutronix.de>
Thanks, applied as f2898449e1df59ef8832cafd411a46ea4c05d0bf.
Michael
[sent from post-receive hook]
On Wed, 08 Feb 2023 12:49:42 +0100, Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> This fixes a copy-n-paste error. <PKG>_LICENSE_FILES is supposed to
> contain a list of files, not <PKG>_LICENSE.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> Message-Id: <20230119162132.133854-1-u.kleine-koenig@pengutronix.de>
> Reviewed-by: Alexander Dahl <ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/doc/dev_licenses.rst b/doc/dev_licenses.rst
> index 0bb1c8d77c5e..6aed9daaca97 100644
> --- a/doc/dev_licenses.rst
> +++ b/doc/dev_licenses.rst
> @@ -195,7 +195,7 @@ Adding license files to PTXdist packages
>
> The SPDX license identifier of the package goes into the ``<PKG>_LICENSE``
> variable in the respective package rule file.
> -All relevant files identified in the steps above are then added to the variable ``<PKG>_LICENSE``,
> +All relevant files identified in the steps above are then added to the variable ``<PKG>_LICENSE_FILES``,
> including a checksum so that PTXdist complains when they change.
>
> Example:
prev parent reply other threads:[~2023-02-08 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 16:21 [ptxdist] [PATCH] " Uwe Kleine-König
2023-01-23 6:53 ` Alexander Dahl
2023-02-08 11:49 ` Michael Olbrich [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=20230208114943.2009054-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=u.kleine-koenig@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