From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Quentin Schulz <quentin.schulz@theobroma-systems.com>
Subject: [mickledore][PATCH 2/7] dev-manual: disk-space: improve wording for obsolete sstate cache files
Date: Wed, 20 Sep 2023 10:07:49 +0200 [thread overview]
Message-ID: <20230920080754.1225508-3-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230920080754.1225508-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Replace "duplicate" by "obsolete", more appropriate.
"duplicate" probably comes from the "--remove-duplicated"
option of the sstate-cache-management.sh script.
Improve other sentences too.
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Richard Purdie <richard.purdie@linuxfoundation.org>
CC: Quentin Schulz <quentin.schulz@theobroma-systems.com>
---
documentation/dev-manual/disk-space.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/dev-manual/disk-space.rst b/documentation/dev-manual/disk-space.rst
index a84bef4511..6d1638a302 100644
--- a/documentation/dev-manual/disk-space.rst
+++ b/documentation/dev-manual/disk-space.rst
@@ -23,12 +23,12 @@ final disk usage of 22 Gbytes instead of &MIN_DISK_SPACE; Gbytes. However,
&MIN_DISK_SPACE_RM_WORK; Gbytes of initial free disk space are still needed to
create temporary files before they can be deleted.
-Purging Duplicate Shared State Cache Files
-==========================================
+Purging Obsolete Shared State Cache Files
+=========================================
After multiple build iterations, the Shared State (sstate) cache can contain
-duplicate cache files for a given package, consuming a substantial amount of
-disk space. However, only the most recent cache files are likeky to be reusable.
+multiple cache files for a given package, consuming a substantial amount of
+disk space. However, only the most recent ones are likely to be reused.
The following command is a quick way to purge all the cache files which
haven't been used for a least a specified number of days::
--
2.34.1
next prev parent reply other threads:[~2023-09-20 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 8:07 [mickledore][PATCH 0/7] mickledore backports michael.opdenacker
2023-09-20 8:07 ` [mickledore][PATCH 1/7] sdk-manual: extensible.rst: fix multiple formatting issues michael.opdenacker
2023-09-20 8:07 ` michael.opdenacker [this message]
2023-09-20 8:07 ` [mickledore][PATCH 3/7] dev-manual: new-recipe.rst fix inconsistency with contributor guide michael.opdenacker
2023-09-20 8:07 ` [mickledore][PATCH 4/7] contributor-guide: recipe-style-guide: add Upstream-Status michael.opdenacker
2023-09-20 8:07 ` [mickledore][PATCH 5/7] dev-manual: licenses: mention SPDX for license compliance michael.opdenacker
2023-09-20 8:07 ` [mickledore][PATCH 6/7] template: fix typo in section header michael.opdenacker
2023-09-20 8:07 ` [mickledore][PATCH 7/7] ref-manual: point outdated link to the new location 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=20230920080754.1225508-3-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=richard.purdie@linuxfoundation.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