From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"Paul Barker" <paul@pbarker.dev>
Cc: "YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] observations on YP overview manual, ch 3
Date: Mon, 27 Oct 2025 11:54:21 +0100 [thread overview]
Message-ID: <DDT1RYTXU693.YS3XUM10ZA81@bootlin.com> (raw)
In-Reply-To: <93d6ba04-0274-74d9-0fc3-b951f089dada@crashcourse.ca>
On Fri Oct 24, 2025 at 11:52 AM CEST, Robert P. J. Day wrote:
> On Fri, 24 Oct 2025, Paul Barker wrote:
>
>> On Thu, 2025-10-23 at 08:40 -0400, Robert P. J. Day wrote:
>> > from here:
>> >
>> > https://docs.yoctoproject.org/overview-manual/development-environment.html#
>> >
>> > * section 3.3, "For any supported release of Yocto Project, you can
>> > also go to the Yocto Project Website and select the “DOWNLOADS” item
>> > from the “SOFTWARE” menu ...". i do not see any link or menu entry
>> > named "SOFTWARE". same claim is made a but further down.
>> >
>> > ah, the graphic on that page shows where it used to be, so that
>> > graphic is clearly out of date.
>> >
>> > i think that's it for that section.
>> >
>> > rday
>>
>> I don't think the website screenshot is adding value to the docs here.
>> We can drop the screenshot and update the text to match the current
>> website.
>>
>> Are you able to send a patch for this?
>
> if people are good with dropping the screenshot, sure, i can provide
> a patch.
I second Paul's suggestion. A patch would be appreciated!
Thanks for the report,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-10-27 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 12:40 observations on YP overview manual, ch 3 Robert P. J. Day
2025-10-24 8:56 ` Paul Barker
2025-10-24 9:54 ` Robert P. J. Day
2025-10-27 10:54 ` Antonin Godard [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=DDT1RYTXU693.YS3XUM10ZA81@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=paul@pbarker.dev \
--cc=rpjday@crashcourse.ca \
/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