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

Re: A few questions about git-reset's reflog messages

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 22, 2011, 20:57 UTC
Message-ID
<7vzkk6vupw.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110722161222.GA20700@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 18 quoted lines
> Subject: [PATCH] reset: give better reflog messages
> ...
> This patch changes the reset reflog code to show:
>
>   $GIT_REFLOG_ACTION: updating {HEAD,ORIG_HEAD}
>
> as before, but only if GIT_REFLOG_ACTION is set. Otherwise,
> show:
>
>    reset: moving to $rev
>
> for HEAD, and:
>
>    reset: updating ORIG_HEAD
>
> for ORIG_HEAD (this is still somewhat superfluous, since we
> are in the ORIG_HEAD reflog, obviously, but at least we now
> mention which command was used to update it).
Looks sensible; thanks.
Previous: Jeff King
Message 3 of 3 in “A few questions about git-reset's reflog messages”
  1. Ori AvtalionJul 21, 2011
  2. Jeff KingJul 22, 2011
  3. Junio C HamanoJul 22, 2011

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.