From: Patrick Steinhardt <ps@pks•im>
To: Junio C Hamano <gitster@pobox•com>
Cc: Ramsay Jones <ramsay@ramsayjones•plus.com>,
GIT Mailing-list <git@vger•kernel.org>
Subject: Re: 'seen' branch identifies as v2.48.0
Date: Tue, 14 Jan 2025 08:51:40 +0100 [thread overview]
Message-ID: <Z4YXjCrtjCUjkEql@pks.im> (raw)
In-Reply-To: <xmqqr0566u60.fsf@gitster.g>
On Mon, Jan 13, 2025 at 05:49:59PM -0800, Junio C Hamano wrote:
> Ramsay Jones <ramsay@ramsayjones•plus.com> writes:
> > I normally like to find solutions before posting problems to the list, but
> > unfortunately I don't have time to look into this at the moment. Sorry!
> >
> > Just a heads up.
>
> I'd throw it back at Patrick, at least for tonight; the topic is
> more or less hot off the press and it should not be surprising it it
> needed immediate fix-up and reroll.
Yup, found the issue. The next version of the Meson series will have it
fixed. Thanks for the report!
Patrick
next prev parent reply other threads:[~2025-01-14 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 1:16 'seen' branch identifies as v2.48.0 Ramsay Jones
2025-01-14 1:49 ` Junio C Hamano
2025-01-14 7:51 ` Patrick Steinhardt [this message]
2025-01-15 3:26 ` Ramsay Jones
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=Z4YXjCrtjCUjkEql@pks.im \
--to=ps@pks$(echo .)im \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=ramsay@ramsayjones$(echo .)plus.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