From: Trevor Woerner <twoerner@gmail.com>
To: Antonin Godard <antonin.godard@bootlin.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] docs: document the conventions used in the manuals
Date: Mon, 31 Aug 2026 09:32:25 -0400 [thread overview]
Message-ID: <apWCaeB2azEgKMlK@localhost.localdomain> (raw)
In-Reply-To: <DL2ZCLBWUBX3.5ITP3G3AJ0SV@bootlin.com>
On Mon 2026-08-31 @ 10:18:42 AM, Antonin Godard wrote:
> Hi,
>
> On Mon Aug 31, 2026 at 5:14 AM CEST, Trevor Woerner via lists.yoctoproject.org wrote:
> > The manuals use angle brackets for placeholders and a prompt to mark a
> > command, and say so nowhere. A reader can only infer both, and one
> > example reads as advice to paste a line that will not parse.
> >
> > Include the new section from every manual, the way the boilerplate is
> > included, so each is self-contained.
>
> We already have a standard.md document that explains these kind of things. I
> think it would be more appropriate to add these conventions there.
Oh, that's interesting, and I hadn't thought of that.
You know how, whenever you pick up any programming book, there's a
section (usually in the Preface) that shows you what typeface is used
for code (versus prose), how a "Warning" admonition is drawn? That's
what I'm trying to recreate here. A "conventions used in this document"
section that is *reader* facing.
What you're pointing at is a *contributor* facing document. And it's a
good point, something should probably be mentioned there so that
contributors follow the same conventions throughout; it helps make the
document look like it was written by one person.
But I feel that a reader-facing conventions section is still warranted.
> Thanks,
> Antonin
next prev parent reply other threads:[~2026-08-31 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 3:14 [PATCH] docs: document the conventions used in the manuals Trevor Woerner
2026-08-31 8:18 ` [docs] " Antonin Godard
2026-08-31 8:20 ` Antonin Godard
2026-08-31 13:32 ` Trevor Woerner [this message]
2026-09-14 16:39 ` Quentin Schulz
2026-09-19 6:17 ` Trevor Woerner
2026-09-21 14:34 ` Antonin Godard
2026-09-22 1:35 ` Trevor Woerner
2026-09-22 7:32 ` Antonin Godard
2026-09-22 11:42 ` Trevor Woerner
[not found] ` <18D6A461E5931E16.876402@lists.yoctoproject.org>
2026-09-20 8:45 ` 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=apWCaeB2azEgKMlK@localhost.localdomain \
--to=twoerner@gmail.com \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.