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>
Subject: Re: [yocto-docs PATCH] dev-manual: bblock: use warning block instead of attention
Date: Fri, 15 Nov 2024 08:48:19 +0100	[thread overview]
Message-ID: <D5ML51LALKU1.2LSUHFK9U8MH1@bootlin.com> (raw)
In-Reply-To: <b5d34c24-48c9-43c8-8891-c350a4a06b1c@cherry.de>

Hi Quentin,

On Thu Nov 14, 2024 at 4:29 PM CET, Quentin Schulz wrote:
> Hi Antonin,
>
> On 11/14/24 4:02 PM, Antonin Godard wrote:
>> Sphinx recommends using warning and note here:
>> https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#directives
>> 
>> Suggested-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> I guess we could have had a commit with more changes in it. Except if 
> your plan is to backport some to earlier releases maybe (since bblock 
> isn't documented/supported in earlier releases)?

It is: in styhead and scarthgap so this patch will be backported there.

> I think it'd be nice also to add this to the standard.md file we have so 
> that people who take the time to read it would know to use these two 
> only going forward?

Ack, I think it's a good idea as well. I'll try to send a patch :)

> Thanks!
> Quentin

Thank you!
Antonin

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



      reply	other threads:[~2024-11-15  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 15:02 [yocto-docs PATCH] dev-manual: bblock: use warning block instead of attention Antonin Godard
2024-11-14 15:29 ` Quentin Schulz
2024-11-15  7:48   ` 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=D5ML51LALKU1.2LSUHFK9U8MH1@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --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