diff mbox series

[v2] dev-manual: correct statements that source is always tarballs

Message ID 82eb83e2-a1ac-ce34-d680-7e4e50caf5a3@crashcourse.ca
State Under Review
Headers show
Series [v2] dev-manual: correct statements that source is always tarballs | expand

Commit Message

Robert P. J. Day June 24, 2025, 8:16 a.m. UTC 
Correct two occurrences that imply source is always fetched as
tarballs.

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

Comments

Quentin Schulz June 24, 2025, 9:48 a.m. UTC | #1 
Hi Robert,

On 6/24/25 10:16 AM, Robert P. J. Day via lists.yoctoproject.org wrote:
> 
> Correct two occurrences that imply source is always fetched as
> tarballs.
> 

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin
diff mbox series

Patch

diff --git a/documentation/dev-manual/efficiently-fetching-sources.rst b/documentation/dev-manual/efficiently-fetching-sources.rst
index a15f0a92c..a3366226c 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 code. For images,
 downloading all the source for various packages can take a significant
 amount of time.

@@ -18,7 +18,7 @@  Setting up Effective Mirrors
 ============================

 A good deal that goes into a Yocto Project build is simply downloading
-all of the source tarballs. Maybe you have been working with another
+source code. Maybe you have been working with another
 build system for which you have built up a
 sizable directory of source tarballs. Or, perhaps someone else has such
 a directory for which you have read access. If so, you can save time by