Re: [PATCH] tag: add tag.createReflog option

From: Cornelius Weig <cornelius.weig@tngtech.com>
Date: Jan 25, 2017, 21:21 UTC
Message-ID: <00712f81-e0ba-52e6-77bc-095a2ed706c4@tngtech.com>
In-Reply-To: <20170125180054.7mioop2o6uvqloyt@sigill.intra.peff.net>

On 01/25/2017 07:00 PM, Jeff King wrote:

Show 12 quoted lines

>   - Is that the end of it, or is the desire really "I want reflogs for
>     _everything_"? That seems like a sane thing to want.
> 
>     If so, then the update to core.logallrefupdates should turn it into
>     a tri-state:
> 
>       - false; no reflogs
> 
>       - true; reflogs for branches, remotes, notes, as now
> 
>       - always; reflogs for all refs under "refs/"
>

I think you nailed it. This is much more useful than what I suggested. I'll see if I can code it up.

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