Yocto Project Documentation
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] i don't see my Oct 1 patch to add Wic as a term
Date: Tue, 10 Nov 2026 16:50:52 +0100	[thread overview]
Message-ID: <DMRNFH1B8TSL.2TXTSH83P6NY3@bootlin.com> (raw)
In-Reply-To: <e059bd28-c55d-2e0b-ad19-b2a13c1df4e6@crashcourse.ca>

On Tue Nov 10, 2026 at 2:09 PM CET, Robert P. J. Day wrote:
> On Tue, 10 Nov 2026, Antonin Godard wrote:
>
>> On Tue Nov 10, 2026 at 11:44 AM CET, Robert P. J. Day wrote:
>> >
>> >   several weeks ago, i submitted a patch to add the "Wic" term to the
>> > ref manual list of terms, and it was signed off:
>> >
>> >   commit 05c97b48227f0e50d008d078b224aa537c06aada
>> >   Author: Robert P. J. Day <rpjday@crashcourse.ca>
>> >   Date:   Thu Oct 1 06:51:58 2026 -0400
>> >
>> >     ref-manual: add a terms entry for Wic
>> >
>> >     Add a short entry for Wic to the reference manual in order to later
>> >     refer to it from other places in the docs.
>> >
>> >     Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>> >     Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> >
>> > but i just checked and don't see it in the official docs (should be
>> > right after "Upstream")
>> >
>> > https://docs.yoctoproject.org/ref-manual/terms.html#term-Upstream
>> >
>> >   i can see that commit in the master branch. am i missing something?
>>
>> This patch was not backported to Blacksail as I didn't think there was a strong
>> need for a backport here.
>>
>> You can see the term on the dev version here:
>> https://docs.yoctoproject.org/dev/ref-manual/terms.html#term-Wic
>>
>> This will display on the default page when Garburn releases.
>
>   ah, got it, i've been out of touch for a few weeks, trying to get
> back into it.  this brings me to my next question -- the whole point
> of adding that Wic term entry was to allow references to "Wic" from
> elsewhere; for example, here:
>
> https://docs.yoctoproject.org/dev/ref-manual/variables.html#term-IMAGE_BOOT_FILES
>
> where you can see, in the first sentence, an obvious candidate for a
> term link:
>
> "A space-separated list of files installed into the boot partition
> when preparing an image using the Wic tool ..."
>                                   ^^^
>
> but once you do that, is it standard practice to introduce the same
> reference *everywhere* in that same section (where "Wic" occurs a
> couple more times)? or is adding the reference only the first time
> in a single section considered sufficient?

I'm pretty sure this is not followed everywhere, and even I sometimes fail to
do so, but we try to reference every occurrence of a word with its corresponding
term when possible. However I feel it might be a little too much sometimes
(twice in the same sentence, for example).

So, up-to-you, you can replace every occurrence mechanically and we can take a
look, but you can also remove excessive replacements, if you have some time.

Thanks,
Antonin

      reply	other threads:[~2026-11-10 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 10:44 i don't see my Oct 1 patch to add Wic as a term Robert P. J. Day
2026-11-10 12:54 ` [docs] " Antonin Godard
2026-11-10 13:09   ` Robert P. J. Day
2026-11-10 15:50     ` Antonin Godard [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=DMRNFH1B8TSL.2TXTSH83P6NY3@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=rpjday@crashcourse.ca \
    /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