From: Antonin Godard <antonin.godard@bootlin.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: docs@lists.yoctoproject.org, yoann.congal@smile.fr
Subject: Re: [docs] [PATCH v2 1/4] migration/release-notes-5.1: document oeqa/selftest envvars change
Date: Tue, 1 Oct 2024 12:30:50 +0200 [thread overview]
Message-ID: <18988e1b-4c41-4363-bcc0-6046c8660c0f@bootlin.com> (raw)
In-Reply-To: <9b2a68da-8ee4-4b1e-935b-c8ae0995aa09@cherry.de>
On 01/10/2024 12:20, Quentin Schulz wrote:
>> Thanks for your reviews, they also help. As for selftest, I haven't seen
>> it referenced with single-tick quotes elsewhere, unless you meant double
>> ticks for code?
>>
>
> I think what we discussed at the time with Michael was basically that
> anything that isn't an English word, or is but shouldn't be understood
> as one in the context (e.g. truncate as in the tool and not the English
> word) should be highlighted so that people don't confuse it with the
> English word.
>
> I think this is what we meant in the standards file here:
> https://git.yoctoproject.org/yocto-docs/tree/documentation/standards.md#n79
Gotcha, single-quote it is indeed.
> Note that these were rules Michael/we came up with for new contributions
> to the docs, because we knew updating everything to match the standards
> would take a long time.
>
> I still remember reading every page of the docs during the migration to
> Sphinx and I am not ready to do this again any time soon :) So patching
> when stumbling upon things that don't match the standard while reading
> the docs and enforcing it for new contributions made sense at the time.
>
> Anyway, that's process and standards, they need to make sense to the
> maintainer and the community, and can evolve over time, so up to you,
> just putting out there the history and "current" state of affairs :)
>
> Since 5.1 is supposed to be out soonish, maybe something to be picky
> about after the release is done ;) Up to you!
Thanks a lot for these details and historical decisions! I will keep
that in mind. I am okay with being picky on this, as it improves the
overall readability of the doc. I'm trying to do that in the release
note I'm editing atm.
Cheers,
Antonin
next prev parent reply other threads:[~2024-10-01 10:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 22:00 [PATCH v2 0/4] Document my team's commits for 5.1 Yoann Congal
2024-09-27 22:00 ` [PATCH v2 1/4] migration/release-notes-5.1: document oeqa/selftest envvars change Yoann Congal
2024-10-01 9:40 ` [docs] " Quentin Schulz
2024-10-01 10:09 ` Antonin Godard
2024-10-01 10:20 ` Quentin Schulz
2024-10-01 10:30 ` Antonin Godard [this message]
2024-10-02 8:57 ` Yoann Congal
2024-10-02 9:35 ` Quentin Schulz
2024-10-03 12:23 ` Improvement of the oeqa/selftest environment variable rewrite change Yoann Congal
2024-09-27 22:00 ` [PATCH v2 2/4] release-notes-5.1: document added python3-libarchive-c ptest Yoann Congal
2024-09-27 22:00 ` [PATCH v2 3/4] release-notes-5.1: document fixed _test_devtool_add_git_url test Yoann Congal
2024-09-27 22:00 ` [PATCH v2 4/4] release-notes-5.1: document spirv-tools reproducibility Yoann Congal
2024-10-01 9:41 ` [docs] " Quentin Schulz
2024-10-01 9:25 ` [docs] [PATCH v2 0/4] Document my team's commits for 5.1 Antonin Godard
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=18988e1b-4c41-4363-bcc0-6046c8660c0f@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--cc=yoann.congal@smile.fr \
/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