From: Nicolas Dechesne <nicolas.dechesne@linaro.org>
To: michael.opdenacker@bootlin.com
Cc: Jose Quaresma <quaresma.jose@gmail.com>,
Paul Barker <paul.barker@sancloud.com>,
"Lee, Chee Yang" <chee.yang.lee@intel.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] [yocto] [ANNOUNCEMENT] Yocto Project 4.0 is Released
Date: Wed, 27 Apr 2022 13:17:42 +0200 [thread overview]
Message-ID: <CAP71Wjw=OL8e=EqgPaLfPbQisTeFuVE2FkXq7+M9nWKckK4Y_Q@mail.gmail.com> (raw)
In-Reply-To: <9790963d-0e8d-c713-cc97-ab6f8ca4fef3@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
On Wed, Apr 27, 2022 at 10:59 AM Michael Opdenacker via
lists.yoctoproject.org <michael.opdenacker=
bootlin.com@lists.yoctoproject.org> wrote:
>
> On 4/27/22 10:18, Jose Quaresma wrote:
> >
> >
> > In the HTML page it is fine, the &YOCTO_DOC_VERSION is 4.0
> >
> https://docs.yoctoproject.org/4.0/migration-guides/migration-4.0.html#release-notes-for-4-0-kirkstone
> >
> > In the dev version the &YOCTO_DOC_VERSION is not replaced by dev
> >
> https://docs.yoctoproject.org/dev/migration-guides/migration-4.0.html#release-notes-for-4-0-kirkstone
>
>
> That's *very weird* because the substitution happened in
> https://docs.yoctoproject.org/dev/brief-yoctoprojectqs/index.html but
> not in
>
> https://docs.yoctoproject.org/dev/migration-guides/migration-4.0.html#release-notes-for-4-0-kirkstone
> (same version).
>
> When I build the docs locally things look fine. Any ideas what could
> cause this?
>
I can reproduce the issue when building locally. I am using Sphinx==4.4.0
>
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#2876):
> https://lists.yoctoproject.org/g/docs/message/2876
> Mute This Topic: https://lists.yoctoproject.org/mt/90726109/1279857
> Group Owner: docs+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [
> nicolas.dechesne@linaro.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 3224 bytes --]
next prev parent reply other threads:[~2022-04-27 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM5PR1101MB236176E376BD554365050E72B9FA9@DM5PR1101MB2361.namprd11.prod.outlook.com>
[not found] ` <9d339a31-a732-3de3-53ee-45a1054d5c92@bootlin.com>
2022-04-27 7:51 ` [docs] [yocto] [ANNOUNCEMENT] Yocto Project 4.0 is Released Richard Purdie
2022-04-27 7:52 ` Michael Opdenacker
[not found] ` <90b05148-5215-584e-0080-24cd411b2ba8@sancloud.com>
[not found] ` <CANPvuR=Sp+tuOAmFRzw207e_1+jNzOyR1AST9J=jh7_KgsOS2Q@mail.gmail.com>
[not found] ` <9790963d-0e8d-c713-cc97-ab6f8ca4fef3@bootlin.com>
2022-04-27 11:17 ` Nicolas Dechesne [this message]
2022-04-27 11:27 ` Nicolas Dechesne
2022-04-27 11:56 ` Nicolas Dechesne
2022-04-27 12:32 ` Michael Opdenacker
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='CAP71Wjw=OL8e=EqgPaLfPbQisTeFuVE2FkXq7+M9nWKckK4Y_Q@mail.gmail.com' \
--to=nicolas.dechesne@linaro.org \
--cc=chee.yang.lee@intel.com \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=paul.barker@sancloud.com \
--cc=quaresma.jose@gmail.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;
as well as URLs for NNTP newsgroup(s).