All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Paul Eggleton <paul.eggleton@linux.microsoft.com>,
	"docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: RE: [docs] [PATCH 3/9] ref-manual: mention wildcarding support in INCOMPATIBLE_LICENSE
Date: Fri, 22 Apr 2022 09:37:15 +0000	[thread overview]
Message-ID: <97f0f040f6e34d439f8cfc169f57c3e2@axis.com> (raw)
In-Reply-To: <ecd878144f6829455df175d4afb0378d43b971ab.1650591341.git.paul.eggleton@linux.microsoft.com>

> -----Original Message-----
> From: docs@lists.yoctoproject.org <docs@lists.yoctoproject.org> On Behalf
> Of Paul Eggleton
> Sent: den 22 april 2022 03:41
> To: docs@lists.yoctoproject.org
> Subject: [docs] [PATCH 3/9] ref-manual: mention wildcarding support in
> INCOMPATIBLE_LICENSE
> 
> From: Paul Eggleton <paul.eggleton@microsoft.com>
> 
> Add this since the INCOMPATIBLE_LICENSE wildcard support has changed in
> the 4.0 release.
> 
> Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
> ---
>  documentation/ref-manual/variables.rst | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index f9fd551..4df8165 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -3485,6 +3485,14 @@ system and gives an overview of their function and contents.
>        incompatible licenses are not built. Packages that are individually
>        licensed with the specified incompatible licenses will be deleted.
> 
> +      There is some support for wildcards in this variable's value,
> +      however it is restricted to specific licenses. Currently only the

Remove "the" at the end.

> +      these wildcards are allowed and expand as follows:
> +
> +      - ``AGPL-3.0*"``: ``AGPL-3.0-only``, ``AGPL-3.0-or-later``
> +      - ``GPL-3.0*``: ``GPL-3.0-only``, ``GPL-3.0-or-later``
> +      - ``LGPL-3.0*``: ``LGPL-3.0-only``, ``LGPL-3.0-or-later``
> +
>        .. note::
> 
>           This functionality is only regularly tested using the following
> --
> 1.8.3.1

//Peter



  reply	other threads:[~2022-04-22 16:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22  1:40 [PATCH 0/9] Release documentation for 4.0 Paul Eggleton
2022-04-22  1:40 ` [PATCH 1/9] migration-3.4: add missing entry on EXTRA_USERS_PARAMS Paul Eggleton
2022-04-22 10:30   ` [docs] " Quentin Schulz
2022-04-22 10:41     ` Richard Purdie
2022-04-22  1:40 ` [PATCH 2/9] ref-manual: add a note about hard-coded passwords Paul Eggleton
2022-04-22  9:35   ` [docs] " Peter Kjellerstedt
2022-04-22  1:40 ` [PATCH 3/9] ref-manual: mention wildcarding support in INCOMPATIBLE_LICENSE Paul Eggleton
2022-04-22  9:37   ` Peter Kjellerstedt [this message]
2022-04-22  1:40 ` [PATCH 4/9] ref-manual: add mention of vendor filtering to CVE_PRODUCT Paul Eggleton
2022-04-22  1:40 ` [PATCH 5/9] ref-manual: add KERNEL_DEBUG_TIMESTAMPS Paul Eggleton
2022-04-22  1:40 ` [PATCH 6/9] ref-manual: add XZ_THREADS and ZSTD_THREADS Paul Eggleton
2022-04-22 10:40   ` [docs] " Quentin Schulz
2022-04-22 11:46     ` Richard Purdie
2022-04-22 12:47       ` Quentin Schulz
2022-04-22 12:50         ` Richard Purdie
2022-04-22  1:40 ` [PATCH 7/9] ref-manual: add empty-dirs QA check and QA_EMPTY_DIRS* Paul Eggleton
2022-04-22  9:50   ` [docs] " Peter Kjellerstedt
2022-04-22 10:51   ` Quentin Schulz
2022-04-22  1:40 ` [PATCH 8/9] migration-guides: complete migration guide for 4.0 Paul Eggleton
2022-04-22 11:10   ` [docs] " Quentin Schulz
2022-04-22 12:09     ` Richard Purdie
2022-04-22  1:40 ` [PATCH 9/9] migration-guides: add release notes " Paul Eggleton
2022-04-22 11:17   ` [docs] " Quentin Schulz
2022-04-22 11:18 ` [docs] [PATCH 0/9] Release documentation " Quentin Schulz

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=97f0f040f6e34d439f8cfc169f57c3e2@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=paul.eggleton@linux.microsoft.com \
    /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.