public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Taylor Blau <me@ttaylorr•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Documentation/RelNotes: use .adoc extension for new security releases
Date: Tue, 08 Jul 2025 13:04:00 -0700	[thread overview]
Message-ID: <xmqqfrf6v49b.fsf@gitster.g> (raw)
In-Reply-To: <d45d881536585ebaaf21ad5089afcd45523df783.1752000456.git.me@ttaylorr.com> (Taylor Blau's message of "Tue, 8 Jul 2025 14:47:50 -0400")

Taylor Blau <me@ttaylorr•com> writes:

> When preparing the latest round of security fixes, we wrote release
> notes in v2.43.7, and then successively merged those up through to the
> various 'maint' branches.
>
> However, the 2.49 release series is the first to have commit 1f010d6bdf
> (doc: use .adoc extension for AsciiDoc files, 2025-01-20). This means
> that we should have renamed the new-but-historical release notes from
> *.txt to *.adoc during the merge into the 'maint-2.49' branch, but
> neglected to do so.
>
> Rename them accordingly to match the convention introduced by
> 1f010d6bdf. Since the release materials in question here were prepared
> before v2.50.0 was tagged, the 'maint' track for that release series is
> OK as is.
>
> Signed-off-by: Taylor Blau <me@ttaylorr•com>
> ---

Thanks.  Will take it directly on top of maint-2.49 branch.

      reply	other threads:[~2025-07-08 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 18:47 [PATCH] Documentation/RelNotes: use .adoc extension for new security releases Taylor Blau
2025-07-08 20:04 ` Junio C Hamano [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=xmqqfrf6v49b.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=me@ttaylorr$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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