($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: simone.p.weiss@posteo.com
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] dev-manual: start.rst: Update use of Download page
Date: Mon, 8 Jan 2024 15:31:20 +0100	[thread overview]
Message-ID: <f9f97504-a57d-4f6a-b988-9f9c9e19cb3b@bootlin.com> (raw)
In-Reply-To: <20231223115124.62413-1-simone.p.weiss@posteo.com>

Hi Simone,

Thanks a lot for the update!

On 23.12.23 at 12:51, simone.p.weiss@posteo.com wrote:
> From: Simone Weiß <simone.p.weiss@posteo.com>
>
> The yocto website has changed its structure. Update the section for
> Accessing the Downloads page to match the new structure.
>
> Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com>
> ---
>   documentation/dev-manual/start.rst | 18 ++++++++++--------
>   1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst
> index 4a556967e..f2027badd 100644
> --- a/documentation/dev-manual/start.rst
> +++ b/documentation/dev-manual/start.rst
> @@ -621,7 +621,7 @@ a selection of these components.
>   Using the Downloads Page
>   ------------------------
>   
> -The :yocto_home:`Yocto Project Website <>` uses a "DOWNLOADS" page
> +The :yocto_home:`Yocto Project Website <>` uses a "RELEASES" page
>   from which you can locate and download tarballs of any Yocto Project
>   release. Rather than Git repositories, these files represent snapshot
>   tarballs similar to the tarballs located in the Index of Releases
> @@ -630,11 +630,13 @@ described in the ":ref:`dev-manual/start:accessing source archives`" section.
>   #. *Go to the Yocto Project Website:* Open The
>      :yocto_home:`Yocto Project Website <>` in your browser.
>   
> -#. *Get to the Downloads Area:* Select the "DOWNLOADS" item from the
> -   pull-down "SOFTWARE" tab menu near the top of the page.
> +#. *Get to the Downloads Area:* Select the "RELEASES" item from the
> +   pull-down "DEVELOPMENT" tab menu near the top of the page.
>   
> -#. *Select a Yocto Project Release:* Use the menu next to "RELEASE" to
> -   display and choose a recent or past supported Yocto Project release
> +#. *Select a Yocto Project Release:* On the top of the "RELEASE" page currently
> +   supported release are displayed, further down past supported Yocto Project


s/release/releases/
I fixed this by myself.

> +   releases are visible. The "Download" links in the rows of the table there
> +   will lead to the download tarballs for the release.
>      (e.g. &DISTRO_NAME_NO_CAP;, &DISTRO_NAME_NO_CAP_MINUS_ONE;, and so forth).
>   
>      .. note::
> @@ -645,9 +647,9 @@ described in the ":ref:`dev-manual/start:accessing source archives`" section.
>      You can use the "RELEASE ARCHIVE" link to reveal a menu of all Yocto
>      Project releases.
>   
> -#. *Download Tools or Board Support Packages (BSPs):* From the
> -   "DOWNLOADS" page, you can download tools or BSPs as well. Just scroll
> -   down the page and look for what you need.
> +#. *Download Tools or Board Support Packages (BSPs):* Next to the tarballs you
> +   will find download tools or BSPs as well. Just select a Yocto Project
> +   release and look for what you need.
>   


Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Merged into master-next, and will backport to other maintained branches.
Thanks again!
Cheers
Michael.

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



      reply	other threads:[~2024-01-08 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 11:51 [PATCH] dev-manual: start.rst: Update use of Download page simone.p.weiss
2024-01-08 14:31 ` 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=f9f97504-a57d-4f6a-b988-9f9c9e19cb3b@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=simone.p.weiss@posteo.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).