All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: michael.opdenacker@bootlin.com,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 1/5] Makefile/set_versions: Allow poky.yaml to be autogenerated
Date: Wed, 23 Mar 2022 10:59:23 +0100	[thread overview]
Message-ID: <95295713-e0e3-66e3-cc86-ea0844c06e32@theobroma-systems.com> (raw)
In-Reply-To: <86e1ecf9-09da-9cd7-347f-637628cbbba4@bootlin.com>

Hi Michael,

On 3/23/22 10:46, Michael Opdenacker via lists.yoctoproject.org wrote:
> Hi Richard,
> 
> On 3/21/22 18:44, Richard Purdie wrote:
>> Use a script to generate the branch/tag information inside poky.yaml.
>>
>> If the branch isn't a known release branch, include git magic to find
>> the closest matching release branch we know about.
>>
>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>> ---
>>   documentation/.gitignore                  |   1 +
>>   documentation/Makefile                    |   1 +
>>   documentation/{poky.yaml => poky.yaml.in} |   0
>>   documentation/set_versions.py             | 115 ++++++++++++++++++++++
>>   4 files changed, 117 insertions(+)
>>   rename documentation/{poky.yaml => poky.yaml.in} (100%)
>>   create mode 100755 documentation/set_versions.py
> 
> A minor issue here: "make clean"  doesn't remove "documentation/poky.yaml" .
> 

This is technically not an issue because open("poky.yaml", "w") 
overwrites the file if it already exists.

Though, we should make sure the run-docs-build script in 
yocto-autobuilder-helper repo actually runs git clean -ffdx before 
checking out another branch otherwise there can be a conflict because 
poky.yaml exists locally and would be overridden/overwritten by 
poky.yaml from an earlier release and fail the checkout. IIRC Richard 
had that in his patch so we should be good.

> What do you prefer? I submit a fix later and we can merge the branch, or
> you propose an update, at least for this patch?

I feel like a fixup patch is just fine, does not seem to be a blocker?

Cheers,
Quentin


  parent reply	other threads:[~2022-03-23  9:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 17:44 [PATCH 0/5 v2] Proposed docs version changes Richard Purdie
2022-03-21 17:44 ` [PATCH 1/5] Makefile/set_versions: Allow poky.yaml to be autogenerated Richard Purdie
     [not found]   ` <86e1ecf9-09da-9cd7-347f-637628cbbba4@bootlin.com>
2022-03-23  9:59     ` Quentin Schulz [this message]
2022-03-21 17:44 ` [PATCH 2/5] conf.py/set_versions/poky.yaml: Set version in conf.py from poky.yaml Richard Purdie
2022-03-21 17:44 ` [PATCH 3/5] set_versions: Add support for setting POKYVERSION found in older releases Richard Purdie
2022-03-21 17:44 ` [PATCH 4/5] set_versions/switchers.js: Allow switchers.js version information to be autogenerated Richard Purdie
2022-03-21 17:44 ` [PATCH 5/5] set_versions: Various improvements Richard Purdie
2022-03-21 21:56 ` [docs] [PATCH 0/5 v2] Proposed docs version changes Nicolas Dechesne
     [not found]   ` <ea41470f551f80509c947bf074eee5b29777953e.camel@linuxfoundation.org>
2022-03-22 13:58     ` Quentin Schulz
2022-03-22 14:25       ` Richard Purdie
2022-03-22 14:33         ` Quentin Schulz
     [not found]           ` <5bdb0cfb67587ad347f17bb59b0ea1b3a3e110b4.camel@linuxfoundation.org>
2022-03-22 14:59             ` Quentin Schulz
     [not found]           ` <16DEBBB55476AD52.11857@lists.yoctoproject.org>
     [not found]             ` <7b263ab8905bc5fe6d2fe6c8cf65bf2583f9ac49.camel@linuxfoundation.org>
2022-03-23  0:47               ` Michael Halstead
2022-03-23 10:15                 ` Richard Purdie

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=95295713-e0e3-66e3-cc86-ea0844c06e32@theobroma-systems.com \
    --to=quentin.schulz@theobroma-systems.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    --cc=richard.purdie@linuxfoundation.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 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.