public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
	<docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Julien Stephan" <jstephan@baylibre.com>
Subject: Re: [PATCH] conf.py: rename :cve: role to :cve_nist:
Date: Mon, 04 Nov 2024 14:31:18 +0100	[thread overview]
Message-ID: <D5DFJNMJZVEW.HSMGI2KFHB0O@bootlin.com> (raw)
In-Reply-To: <c329c77d-b5cc-4a28-a345-ac4261a70d3c@cherry.de>

On Mon Nov 4, 2024 at 1:55 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 11/4/24 1:39 PM, Antonin Godard wrote:
>> Newer versions of Sphinx already define a :cve: role that points to
>> cve.org, instead of the role we defined in conf.py that points to
>> nvd.nist.gov.
>> 
>> Rename our role to :cve_nist: to avoid warnings (treated as errors).
>> This is also backwards compatible, meaning we can build the doc with an
>> older Sphinx if needed.
>> 
>> Suggested-By: Quentin Schulz <quentin.schulz@cherry.de>
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>
> Looks good to me. I assume you didn't change those by hand, maybe add 
> the command you used to do the migration so we can figure out if 
> something's been left out inadvertently? (Would be useful if we figure 
> out in the future that this missed something so we can more easily find 
> a programmatic way of fixing the left-out instead of finding and fixing 
> them by hand?).

Hmm... I used my editor, but the equivalent one-liner is:

find . -name '*.rst' -exec sed -i 's/:cve:/:cve_nist:/g' {} \+

Which I'll add to the commit message.

> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> (Admittedly only reviewed the conf.py part :) ).
>
> For backporting, we'll likely need a new patch on the autobuilder, c.f. 
> https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/docs-build-patches 
> since we want to build tags which we cannot move.

If I understand correctly, these are patches to apply to old documentation
versions? To extend my reasoning on this, since new tags were added recently for
old doc versions, should I update `missing_tags` and add corresponding patches
there? I'm a bit clueless :)

> Thanks!
> Quentin

Thank you,
Antonin

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



  reply	other threads:[~2024-11-04 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 12:39 [PATCH] conf.py: rename :cve: role to :cve_nist: Antonin Godard
2024-11-04 12:55 ` Quentin Schulz
2024-11-04 13:31   ` Antonin Godard [this message]
2024-11-04 14:06     ` Quentin Schulz
2024-11-04 14:26       ` 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=D5DFJNMJZVEW.HSMGI2KFHB0O@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=jstephan@baylibre.com \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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