public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Justin Bronder <jsbronder@cold-front.org>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] contributor-guide: add License-Update tag
Date: Wed, 22 Nov 2023 21:23:25 +0100	[thread overview]
Message-ID: <1ac621f7-085d-4e05-9a13-4fa183e2bcb0@bootlin.com> (raw)
In-Reply-To: <20231121195854.27968-1-jsbronder@cold-front.org>

Hi Justin,

Many thanks for this improvement to the docs.

On 21.11.23 at 20:58, Justin Bronder wrote:
> Porting from the old wiki
> https://www.openembedded.org/index.php?title=Commit_Patch_Message_Guidelines&oldid=10935#Describing_license_changes
>
> Signed-off-by: Justin Bronder <jsbronder@cold-front.org>
> ---
>   .../contributor-guide/recipe-style-guide.rst          | 11 +++++++++++
>   1 file changed, 11 insertions(+)
>
> diff --git a/documentation/contributor-guide/recipe-style-guide.rst b/documentation/contributor-guide/recipe-style-guide.rst
> index a005aa324..bb8f6980e 100644
> --- a/documentation/contributor-guide/recipe-style-guide.rst
> +++ b/documentation/contributor-guide/recipe-style-guide.rst
> @@ -250,6 +250,17 @@ Recipes need to define both the :term:`LICENSE` and
>      correct string that you can substitute into the recipe file for a
>      subsequent build.
>   
> +License Updates
> ++++++++++++++++

I just replaced "++++..." by "~~~~..." as recommended in 
documentation/README and used in other parts of the manual, though the 
result looks the same to create a subsection.
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Merged into "master-next".

Thanks again
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2023-11-22 20:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 19:58 [PATCH] contributor-guide: add License-Update tag Justin Bronder
2023-11-22 20:23 ` Michael Opdenacker [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=1ac621f7-085d-4e05-9a13-4fa183e2bcb0@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=jsbronder@cold-front.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