Re: [PATCH v2 4/8] builtin/reflog: implement subcommand to write new entries

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Jul 29, 2025, 06:14 UTC
Message-ID: <6cb4522b-43f0-4b0b-9dbf-4f10c8c94487@app.fastmail.com>
In-Reply-To: <6E84D571-CC02-45E6-9E58-DD918B45998E@gmail.com>

On Tue, Jul 29, 2025, at 02:25, Ben Knoble wrote:

Show 8 quoted lines

>> ...
>> Will show one entry since `branch` is the one-level ref `branch`, not
>> `refs/heads/branch`.  Now it looks like `write` truncated the reflog and
>> wrote a new reflog message (if you mistakenly think that `branch` is a
>> branch).
>
> This quirk of update-ref bit me the first few times I used it, too. I
> think it’s at least documented there though.

I do that with update-ref more than I care to commit^W admit. But that’s consistent with the command and well-documented.

$ 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.