git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUGS] Git v2.51.2 on NonStop

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Oct 30, 2025, 20:25 UTC
Message-ID
<3dad5cb9-976b-4e60-9e6e-05c12c7d9f2d@app.fastmail.com>
In-Reply-To
<xmqqecqk5g7r.fsf@gitster.g>
On Thu, Oct 30, 2025, at 20:42, Junio C Hamano wrote:
Show 18 quoted lines
> "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.
Previous: Junio C HamanoNext: rsbecker@nexbridge.com
Message 14 of 18 in “[ANNOUNCE] Git v2.51.2”
  1. Junio C HamanoOct 27, 2025
  2. [BUGS] Git v2.51.2 on NonStoprsbecker@nexbridge.com, Oct 28, 2025
  3. SZEDER GáborOct 29, 2025
  4. rsbecker@nexbridge.comOct 29, 2025
  5. SZEDER GáborOct 29, 2025
  6. rsbecker@nexbridge.comOct 30, 2025
  7. Jeff KingOct 30, 2025
  8. D. Ben KnobleOct 30, 2025
  9. rsbecker@nexbridge.comOct 30, 2025
  10. brian m. carlsonOct 30, 2025
  11. Kristoffer HaugsbakkOct 30, 2025
  12. rsbecker@nexbridge.comOct 30, 2025
  13. Junio C HamanoOct 30, 2025
  14. Kristoffer HaugsbakkOct 30, 2025
  15. rsbecker@nexbridge.comOct 30, 2025
  16. SZEDER GáborOct 30, 2025
  17. rsbecker@nexbridge.comOct 31, 2025
  18. rsbecker@nexbridge.comOct 31, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.