All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Subject: Re: [PATCH 3/5] doc: develop: codingstyle: Update b4 external link
Date: Wed, 21 Jan 2026 11:58:38 +0100	[thread overview]
Message-ID: <6841ded9-e35b-424e-83ea-090c64d3e2de@cherry.de> (raw)
In-Reply-To: <20260120223405.469050-4-trini@konsulko.com>

Hi Tom,

On 1/20/26 11:31 PM, Tom Rini wrote:
> Rather than pointing at the source code for b4, point the the official
> documentation. Also, use an anonymous reference for the link, per rST
> best practices.
> 

TIL :)

> Signed-off-by: Tom Rini <trini@konsulko.com>

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

  reply	other threads:[~2026-01-21 10:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 22:31 [PATCH 0/5] doc: develop: Document b4 for custodians Tom Rini
2026-01-20 22:31 ` [PATCH 1/5] doc: develop: process: Move Custodians section Tom Rini
2026-01-21 10:55   ` Quentin Schulz
2026-01-20 22:31 ` [PATCH 2/5] doc: develop: process: Make "Work flow of a Custodian" a subsection Tom Rini
2026-01-21  9:44   ` Michael Nazzareno Trimarchi
2026-01-21 14:51     ` Tom Rini
2026-01-21 10:57   ` Quentin Schulz
2026-01-20 22:31 ` [PATCH 3/5] doc: develop: codingstyle: Update b4 external link Tom Rini
2026-01-21 10:58   ` Quentin Schulz [this message]
2026-01-20 22:31 ` [PATCH 4/5] doc: develop: sending_patches: Update link to patchwork Tom Rini
2026-01-21 10:59   ` Quentin Schulz
2026-01-20 22:31 ` [PATCH 5/5] doc: develop: process: Document using b4 and patchwork for custodians Tom Rini
2026-01-21 11:16   ` Quentin Schulz
2026-01-21 15:06     ` Tom Rini
2026-01-26 13:17       ` Mattijs Korpershoek
2026-01-26 13:18   ` Mattijs Korpershoek

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=6841ded9-e35b-424e-83ea-090c64d3e2de@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.