Re: [docs] [PATCH] ref-manual/qa-checks.rst: fix references

["Antonin Godard" <antonin.godard@bootlin.com>]

On Wed Oct 8, 2025 at 4:35 PM CEST, Quentin Schulz via lists.yoctoproject.org wrote:
[...]
> For consistency sake, should we always have the error message in a list 
> even if there's only one per section? e.g. ``arch`` has multiple entries 
> in the subsection so we have a dash to specify the start of an item in 
> the list, but ``already-stripped`` only has one, and with the current 
> patch, we don't have a list. Which means a different indentation both in 
> source and in rendered form.

I purposefully created lists only for sections that had multiple possibilities
of error messages. I figured it wasn't necessary to start a list with a single
item.

> [...]
>
>>   .. _qa-check-configure-gettext:
>>   
>> --  ``AM_GNU_GETTEXT used but no inherit gettext [configure-gettext]``
>> +``configure-gettext``
>> +---------------------
>>   
>> -    If a recipe is building something that uses automake and the automake
>> -    files contain an ``AM_GNU_GETTEXT`` directive then this check will fail
>> -    if there is no ``inherit gettext`` statement in the recipe to ensure
>> -    that gettext is available during the build. Add ``inherit gettext`` to
>> -    remove the warning.
>> +``AM_GNU_GETTEXT used but no inherit gettext [configure-gettext]``
>> +
>> + If a recipe is building something that uses automake and the automake
>> + files contain an ``AM_GNU_GETTEXT`` directive then this check will fail
>> + if there is no ``inherit gettext`` statement in the recipe to ensure
>> + that gettext is available during the build. Add ``inherit gettext`` to
>> + remove the warning.
>
> Spurious leading whitespace for the whole paragraph.

Thanks! I tried to remove all of those but missed that one.
Looking for other "^ [a-zA-Z0-9]" patterns I couldn't find any other occurences.

I'll send a v2.

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com