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

Re: [PATCH] t1400: fix --no-create-reflog test and description

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 8, 2024, 03:13 UTC
Message-ID
<xmqqwmhepgcw.fsf@gitster.g>
In-Reply-To
<4e68a04f-fb5e-49f9-8ba2-661027d8165d@app.fastmail.com>
"Kristoffer Haugsbakk" <code@khaugsbakk.name> writes:
> I didn’t get the impression that this is expecting a reroll.  But I
> haven’t seen it mentioned or applied to `seen`/`next`?

If the interim maintainer did not think it is ready to be queued to 'seen', I won't go back to the list archive to pick it up (after all, that is part of trusting interim maintainer is about---otherwise I have to go back and consume all the list backlog, which does not make sense).

If a topic is worth resurrecting, do resend it for discussion. Looking at the archived discussion (for this topic I am making an exception), I did not get an impression that this got a "yeah this is a good thing to do" support, only a lukewarm "it may be a starting point in a good direction".

Thanks.
Previous: Kristoffer Haugsbakk
Message 8 of 8 in “t1400: fix --no-create-reflog test and description”
  1. t1400: fix --no-create-reflog test and descriptionkristofferhaugsbakk@fastmail.com, Oct 20, 2024
  2. Patrick SteinhardtOct 21, 2024
  3. Kristoffer HaugsbakkOct 21, 2024
  4. Taylor BlauOct 21, 2024
  5. Kristoffer HaugsbakkOct 21, 2024
  6. Taylor BlauOct 21, 2024
  7. Kristoffer HaugsbakkNov 7, 2024
  8. Junio C HamanoNov 8, 2024

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.