All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: yocto@lists.yoctoproject.org, docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH yocto-autobuilder-helper] scripts/run-docs-build: make all versions list releases known to master
Date: Wed, 8 Dec 2021 18:27:44 +0100	[thread overview]
Message-ID: <1e09381f-6650-9b99-748a-477f19642970@bootlin.com> (raw)
In-Reply-To: <20211203093400.gzqddyn3vbrm256a@fedora>

Hi Quentin,

Thanks for the review and for your suggestions.

On 12/3/21 10:34 AM, Quentin Schulz wrote:
> Hi Michael,
>
> On Wed, Dec 01, 2021 at 02:49:31PM +0100, Michael Opdenacker wrote:
>> This allows all versions of Bitbake and Yocto Project manuals
>> to see the manuals for the latest versions.
>>
>> This also simplifies the release process, not having to update the
>> releases.rst file for all releases every time a new release is made.
>>
>> Note that such synchronization is already done for the
>> switchers.js file (but in a different way). This way, advertised
>> releases are in sync with switchers.js.
>>
> Why don't we migrate this different method (find) to the one you
> implement in this commit too?
>
> I could see a variable storing all "force-latest" files or someting like
> that to make it obvious why they have a specific handling.


I tried, but I stumble on the need to copy the latest switchers.js from
yocto-docs to the Bitbake branches too.

And since the Bitbake branches need to be checked out and processed
first, I hesitate to add a special extra step to checkout the yocto-docs
repo before. Possible but adding complexity.

So, if I don't use this way for the Bitbake branches, I still need a
find command at the end...

If you don't think about any better idea, I'd propose to stick to this
version of the patch.

Cheers
Michael.

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



      reply	other threads:[~2021-12-08 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 13:49 [PATCH yocto-autobuilder-helper] scripts/run-docs-build: make all versions list releases known to master Michael Opdenacker
2021-12-03  9:34 ` [docs] " Quentin Schulz
2021-12-08 17:27   ` 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=1e09381f-6650-9b99-748a-477f19642970@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --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 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.