From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Quentin Schulz <foss@0leil.net>,
docs@lists.yoctoproject.org, yocto@lists.yoctoproject.org
Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Subject: Re: [docs] [PATCH] auto-generate releases.rst
Date: Tue, 19 Jul 2022 11:16:31 +0200 [thread overview]
Message-ID: <7981ea5f-0388-4a80-1d50-b4994e215a04@bootlin.com> (raw)
In-Reply-To: <20220719081214.1924835-1-foss+yocto@0leil.net>
Hi Quentin
On 7/19/22 10:12, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
>
> In order to maintain one less file, let's auto-generate the releases.rst
> file which contains a link for each release ever released.
>
> This gets auto-generated by checking the tags available in this git repo
> and adding a link for each that exists.
>
> A few tags are notoriously missing from this git repo and they are
> manually listed then, until the tags are pushed for the appropriate
> commit.
That's brilliant, thanks a lot!
Just a few comments below...
> ")
>
> +# generate releases.rst
Don't forget to add your name to the authors at the beginning of the
script and what the script does now.
Thanks again!
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-07-19 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 8:12 [PATCH] auto-generate releases.rst Quentin Schulz
2022-07-19 8:12 ` [PATCH yocto-autobuilder-helper 1/2] scripts: run-docs-build: use latest version of set_versions.py script Quentin Schulz
2022-07-19 8:12 ` [PATCH yocto-autobuilder-helper 2/2] scripts/run-docs-build: do not checkout releases.rst from master anymore Quentin Schulz
2022-07-20 13:12 ` [docs] " Michael Opdenacker
2022-07-19 9:16 ` 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=7981ea5f-0388-4a80-1d50-b4994e215a04@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=foss@0leil.net \
--cc=quentin.schulz@theobroma-systems.com \
--cc=yocto@lists.yoctoproject.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