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

Re: [PATCH] reset: avoid reflog update on no-op reset

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 23, 2026, 16:18 UTC
Message-ID
<xmqq7bt8joae.fsf@gitster.g>
In-Reply-To
<SL2P216MB1885C5C9B75A38AE99E5511DA294A@SL2P216MB1885.KORP216.PROD.OUTLOOK.COM>
Pushkar Singh <pushkarkumarsingh1970@gmail.com> writes:
> ... or to rework it in a way that preserves the reflog
> entry while addressing the underlying concern (if there is one).

I am OK as long as this patch does not come back in its current form ;-), but it is curious what "the underlying concern" is. It sounds like you see some problems that need to be addressed if the current "the act of resetting to the same commit is recorded in the reflog", but I am not sure what they are.

Thanks.
Previous: Pushkar Singh
Message 2 of 2 in “Re: [PATCH] reset: avoid reflog update on no-op reset”
  1. Pushkar SinghJan 23, 2026
  2. Junio C HamanoJan 23, 2026

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.