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

Re: create reflog for reflog-less ref

From
Chris Jerdonek <chris.jerdonek@gmail.com>
Date
Feb 26, 2020, 10:21 UTC
Message-ID
<CAOTb1weTWOsHkbGqmj8mJ-KpkoiteHBDYDxe-j2E0yf3DccjjQ@mail.gmail.com>
In-Reply-To
<20200226094716.GA14546@coredump.intra.peff.net>
On Wed, Feb 26, 2020 at 1:47 AM Jeff King <peff@peff.net> wrote:
Show 11 quoted lines
> On Tue, Feb 25, 2020 at 11:18:39PM -0800, Chris Jerdonek wrote:
> > It would be
> > nice to be able to create (or append to) the reflog without having to
> > change where the ref is pointing. Or maybe I'm missing a variation
> > that will do this..
> ...
> The "touch" trick I showed would work for that, but it's not going to be
> portable going forward. I don't think it would be a bad idea to have
> some way of triggering a "noop" reflog update via update-ref, where we
> either create the reflog as empty, or insert a pointless entry going
> from the current sha1 to itself. But AFAIK that doesn't exist right now.
Thanks. By the way, this functionality does already seem to exist for ref HEAD:

$ git update-ref -m my-message HEAD HEAD $ git reflog HEAD 3ccacdc (HEAD -> master) HEAD@{0}: my-message ...

I don't know why it would work for HEAD though and what's different about the mechanism. I thought it might be because it's a symbolic ref, but it didn't work for other symbolic refs when I tried (even ones that already had a reflog).

--Chris
Previous: Jeff KingNext: Jeff King
Message 6 of 7 in “create reflog for reflog-less ref”
  1. Chris JerdonekFeb 26, 2020
  2. brian m. carlsonFeb 26, 2020
  3. Jeff KingFeb 26, 2020
  4. Chris JerdonekFeb 26, 2020
  5. Jeff KingFeb 26, 2020
  6. Chris JerdonekFeb 26, 2020
  7. Jeff KingFeb 26, 2020

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.