From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: michael.opdenacker@bootlin.com, docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] dev-manual: packages: clarify shared PR service constraint
Date: Mon, 4 Mar 2024 12:19:49 +0100 [thread overview]
Message-ID: <960a8905-4c6d-47e2-b1c6-ad337b628e71@theobroma-systems.com> (raw)
In-Reply-To: <20240221211648.104003-1-michael.opdenacker@bootlin.com>
Hi Michael,
On 2/21/24 22:16, Michael Opdenacker via lists.yoctoproject.org wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> Explicit the problems previous described as "obvious".
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> ---
> documentation/dev-manual/packages.rst | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/documentation/dev-manual/packages.rst b/documentation/dev-manual/packages.rst
> index 0e991e409a..d90ff7110e 100644
> --- a/documentation/dev-manual/packages.rst
> +++ b/documentation/dev-manual/packages.rst
> @@ -205,9 +205,14 @@ history, see the
> The OpenEmbedded build system does not maintain :term:`PR` information as
> part of the shared state (sstate) packages. If you maintain an sstate
> feed, it's expected that either all your building systems that
> - contribute to the sstate feed use a shared PR Service, or you do not
> - run a PR Service on any of your building systems. Having some systems
> - use a PR Service while others do not leads to obvious problems.
> + contribute to the sstate feed use a shared PR service, or you do not
> + run a PR Service on any of your building systems.
> +
The first line makes service lowercase, while the second line is
capitalized.
> + That's because if you had multiple machines sharing a PR service but > + not their sstate feed, you could end up with "diverging" hashes for
> + the same output artefacts. When presented to the share PR service,
Here lowercase as well, so I guess we wanted lowercase in the second (+)
line above?
Cheers,
Quentin
prev parent reply other threads:[~2024-03-04 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 21:16 [PATCH] dev-manual: packages: clarify shared PR service constraint michael.opdenacker
2024-03-04 11:19 ` Quentin Schulz [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=960a8905-4c6d-47e2-b1c6-ad337b628e71@theobroma-systems.com \
--to=quentin.schulz@theobroma-systems.com \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.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).