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

Re: [PATCH] Support ref logs for refs/*

From
Nanako Shiraishi <nanako3@lavabit.com>
Date
Jan 8, 2009, 09:08 UTC
Message-ID
<20090108180857.6117@nanako3.lavabit.com>
In-Reply-To
<20090108082827.GA6177@tesla.theory.org>
Quoting Neil Macneale <mac4-git@theory.org>:
> The documentation for git update-ref seems to imply that logging of ref
> updates should be done for anything in refs/...
The documementation for git-update-ref is part of git, and git does not use anything outside of refs/{heads,tags,remotes}/ for its normal operation. 
I think it is generally assumed that there is nothing of interest outside of these areas that deserves the automated creation of reflogs, and the code you are touching is about that. Once you have reflog for any ref you are interested outside of these areas, your actions will be logged regardless. 
Most notably, refs/stash itself is exempt from this code path and it makes sure that reflog exists without relying on log_all_ref_updates configuration. 
Also the documentation for the configuration variable explicitly says it is about the branch heads.
core.logAllRefUpdates::
	Enable the reflog. Updates to a ref <ref> is logged to the file
	"$GIT_DIR/logs/<ref>", by appending the new and old
	SHA1, the date/time and the reason of the update, but
	only when the file exists.  If this configuration
	variable is set to true, missing "$GIT_DIR/logs/<ref>"
	file is automatically created for branch heads.
-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
Previous: Neil MacnealeNext: mac4-git@theory.org
Message 2 of 3 in “Support ref logs for refs/*”
  1. Support ref logs for refs/*Neil Macneale, Jan 8, 2009
  2. Nanako ShiraishiJan 8, 2009
  3. mac4-git@theory.orgJan 8, 2009

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.