From: Trevor Woerner <twoerner@gmail.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH v2 6/8] docs: remove real accounts from the examples
Date: Thu, 24 Sep 2026 11:55:40 -0400 [thread overview]
Message-ID: <arVH_CL40IlR7ZY_@localhost.localdomain> (raw)
In-Reply-To: <8c5111cf-4018-4e01-9043-b4c567091d75@cherry.de>
On Wed 2026-09-23 @ 01:02:05 PM, Quentin Schulz wrote:
> Hi Trevor,
>
> On 9/22/26 8:32 PM, Trevor Woerner via lists.yoctoproject.org wrote:
> > Examples across the manuals carry the account names of the people who
> > wrote them, in home directory paths and in shell prompts that also
> > name a machine. Use "/home/user" and a bare "$", which is what the rest
> > of the manuals already do.
> >
> > The autobuilder's own service account is left alone: the paths containing
> > it are about autobuilder output rather than about somebody's machine.
> >
> > AI-Generated: codex/claude-opus 5 (xhigh)
> > Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> > ---
> > changes in v2:
> > - rebased on master-next; no other change
> > ---
> [...]
> > diff --git a/documentation/dev-manual/layers.rst b/documentation/dev-manual/layers.rst
> > index 185a63feb700..a36f849a0c3f 100644
> > --- a/documentation/dev-manual/layers.rst
> > +++ b/documentation/dev-manual/layers.rst
> [...]
> > @@ -958,7 +958,7 @@ above:
> > #. Run the script directly with no options::
> > - alex@Zen2:/srv/work/alex/my-build$ meta-alex/setup-layers
> > + $ meta-alex/setup-layers
>
> No, the path is known there and is important. If you prefer, you can modify
> /srv/work/alex/meta-alex all over the file to something that works better
> for you, but the path in the prompt is important.
Okay.
> Cheers,
> Quentin
next prev parent reply other threads:[~2026-09-24 15:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 18:32 [PATCH v2 0/8] docs: editorial repairs to the examples Trevor Woerner
2026-09-22 18:32 ` [PATCH v2 1/8] docs: give the root prompts a preamble Trevor Woerner
2026-09-23 10:17 ` [docs] " Quentin Schulz
2026-09-24 16:00 ` Trevor Woerner
2026-09-22 18:32 ` [PATCH v2 2/8] docs: copy only the command from a console block Trevor Woerner
2026-09-23 10:41 ` [docs] " Quentin Schulz
2026-09-23 10:43 ` Quentin Schulz
2026-09-22 18:32 ` [PATCH v2 3/8] docs: show a prompt on commands the reader is meant to type Trevor Woerner
2026-09-23 10:49 ` [docs] " Quentin Schulz
2026-09-24 15:59 ` Trevor Woerner
2026-09-22 18:32 ` [PATCH v2 4/8] docs: write an elided passage as a comment Trevor Woerner
2026-09-23 10:50 ` [docs] " Quentin Schulz
2026-09-22 18:32 ` [PATCH v2 5/8] docs: mark the placeholders in examples Trevor Woerner
2026-09-23 10:57 ` [docs] " Quentin Schulz
2026-09-24 15:58 ` Trevor Woerner
2026-09-22 18:32 ` [PATCH v2 6/8] docs: remove real accounts from the examples Trevor Woerner
2026-09-23 11:02 ` [docs] " Quentin Schulz
2026-09-24 15:55 ` Trevor Woerner [this message]
2026-09-22 18:32 ` [PATCH v2 7/8] kernel-dev: give each example block one thing to hold Trevor Woerner
2026-09-23 11:05 ` [docs] " Quentin Schulz
2026-09-22 18:32 ` [PATCH v2 8/8] ref-manual: put the ARCHIVER_MODE comments on their own lines Trevor Woerner
2026-09-23 11:09 ` [docs] " Quentin Schulz
2026-09-24 15:55 ` Trevor Woerner
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=arVH_CL40IlR7ZY_@localhost.localdomain \
--to=twoerner@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
/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