From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Junio C Hamano" <gitster@pobox•com>
Cc: rsbecker <rsbecker@nexbridge•com>, git@vger•kernel.org
Subject: Re: [BUGS] Git v2.51.2 on NonStop
Date: Thu, 30 Oct 2025 21:25:42 +0100 [thread overview]
Message-ID: <3dad5cb9-976b-4e60-9e6e-05c12c7d9f2d@app.fastmail.com> (raw)
In-Reply-To: <xmqqecqk5g7r.fsf@gitster.g>
On Thu, Oct 30, 2025, at 20:42, Junio C Hamano wrote:
> "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com> writes:
>
>> On Tue, Oct 28, 2025, at 18:40, rsbecker@nexbridge•com wrote:
>>>[snip]
>>
>> Would it make sense for maintenance releases to have a small release
>> candidate pre-release? Both of these maintenance releases have had
>> issues.
>
> Well, that is usually called "the tip of 'master'". Has NonStop
> been having issues with the tip of 'master'? For how long? Why
> haven't we heard about it at all? After things are merged there
> (which requires them to be cooking in 'next'---oh, has NonStop been
> having issues with 'next'? For how long?), only fixes are chosen
> and merged to 'maint' to be the next maintenance release.
> ...
> I doubt any pre-release on 'maint' has much value in that anybody who
> are not testing the tip of 'master' would not be testing it either.
You are probably 99.9% likely to be correct.
next prev parent reply other threads:[~2025-10-30 20:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 15:56 [ANNOUNCE] Git v2.51.2 Junio C Hamano
2025-10-28 17:40 ` [BUGS] Git v2.51.2 on NonStop rsbecker
2025-10-29 22:28 ` SZEDER Gábor
2025-10-29 22:41 ` rsbecker
2025-10-29 23:18 ` SZEDER Gábor
2025-10-30 0:24 ` rsbecker
2025-10-30 2:53 ` Jeff King
2025-10-30 13:52 ` D. Ben Knoble
2025-10-30 14:59 ` rsbecker
2025-10-30 21:23 ` brian m. carlson
2025-10-30 15:15 ` Kristoffer Haugsbakk
2025-10-30 16:02 ` rsbecker
2025-10-30 19:42 ` Junio C Hamano
2025-10-30 20:25 ` Kristoffer Haugsbakk [this message]
2025-10-30 21:46 ` [BUGS] Git v2.51.2 on NonStop5 rsbecker
2025-10-30 22:30 ` SZEDER Gábor
2025-10-31 1:02 ` rsbecker
2025-10-31 14:09 ` rsbecker
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=3dad5cb9-976b-4e60-9e6e-05c12c7d9f2d@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=rsbecker@nexbridge$(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