From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] dev-manual: correct statement that source is always tarballs
Date: Tue, 24 Jun 2025 09:47:21 +0200 [thread overview]
Message-ID: <DAULIP34CY9R.QQ612GXE94MA@bootlin.com> (raw)
In-Reply-To: <9c2b4c83-b40a-4f21-1680-e95a9e238a82@crashcourse.ca>
On Sun Jun 22, 2025 at 4:50 PM CEST, Robert P. J. Day wrote:
>
> It's misleading to suggest that source is always fetched as tarballs.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/documentation/dev-manual/efficiently-fetching-sources.rst b/documentation/dev-manual/efficiently-fetching-sources.rst
> index a15f0a92c..2f8a68e20 100644
> --- a/documentation/dev-manual/efficiently-fetching-sources.rst
> +++ b/documentation/dev-manual/efficiently-fetching-sources.rst
> @@ -6,7 +6,7 @@ Efficiently Fetching Source Files During a Build
> The OpenEmbedded build system works with source files located through
> the :term:`SRC_URI` variable. When
> you build something using BitBake, a big part of the operation is
> -locating and downloading all the source tarballs. For images,
> +locating and downloading all of the source. For images,
This is also present slightly below, in the same document. Can you replace that
occurence too?
Also I would suggest "all of the source code" instead of "all of the source".
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-06-24 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 14:50 [PATCH] dev-manual: correct statement that source is always tarballs Robert P. J. Day
2025-06-23 14:19 ` [docs] " Quentin Schulz
2025-06-24 7:47 ` 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=DAULIP34CY9R.QQ612GXE94MA@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--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 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.