public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	docs@lists.yoctoproject.org
Cc: michael.opdenacker@bootlin.com,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [docs] [PATCH] dev-manual: disk-space: improve wording for obsolete sstate cache files
Date: Mon, 18 Sep 2023 17:28:30 +0200	[thread overview]
Message-ID: <a7366b33-b6f2-a79b-9bc4-7b6ce8eaa310@bootlin.com> (raw)
In-Reply-To: <c98cbf98-0335-d559-6673-7348b4e4295c@theobroma-systems.com>

Hi Quentin,

Thanks for the review!

On 18.09.23 at 17:14, Quentin Schulz wrote:
> Hi Michael,
>
> On 9/18/23 17:09, Michael Opdenacker via lists.yoctoproject.org wrote:
>> 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>
>> ---
>>   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..5b6702f594 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 likeky to be 
>> reusable.
>
> s/likeky/likely/


Oops, fixed!

>
> s/reusable/reused/

I was going to say that I prefer "reusable", but I guess you meant that 
the combination of "likely" and "reusable" is applying the possibility 
twice.

OK for "reused" too.

Thanks again!
Michael.

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



  reply	other threads:[~2023-09-18 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 15:09 [PATCH] dev-manual: disk-space: improve wording for obsolete sstate cache files michael.opdenacker
2023-09-18 15:14 ` [docs] " Quentin Schulz
2023-09-18 15:28   ` Michael Opdenacker [this message]
2023-09-18 15:31     ` Quentin Schulz

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=a7366b33-b6f2-a79b-9bc4-7b6ce8eaa310@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