U-Boot Archive on 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] doc: release_cycle: Use variable substitution for next version
Date: Tue, 8 Apr 2025 16:03:11 +0200	[thread overview]
Message-ID: <484017a4-956f-4b1b-bebf-cab6dcfa860e@cherry.de> (raw)
In-Reply-To: <20250408135421.1393991-1-trini@konsulko.com>

Hi Tom,

On 4/8/25 3:54 PM, Tom Rini wrote:
> To avoid the problem fixed in commit 57a95d522ca8 ("doc: release_cycle:
> fix next release version") moving forward, make use of the variable
> substitution feature of rST. This adds a next_ver variable and
> references it in all of the places where I had been listing the version
> being worked on.
> 
> Suggested-by: Quentin Schulz <quentin.schulz@cherry.de>

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

Thanks!
Quentin

      reply	other threads:[~2025-04-08 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 13:54 [PATCH] doc: release_cycle: Use variable substitution for next version Tom Rini
2025-04-08 14:03 ` Quentin Schulz [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=484017a4-956f-4b1b-bebf-cab6dcfa860e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox