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

[PATCH] Add the word reflog to Documentation/config.txt:core.logAllRefUpdates

From
Lukas Sandström <lukass@etek.chalmers.se>
Date
Aug 19, 2007, 21:38 UTC
Message-ID
<46C8B871.9030408@etek.chalmers.se>

This makes it easier to find out how to enable the reflog for a bare repository by searching the documentation for "reflog".

Signed-off-by: Lukas Sandström <lukass@etek.chalmers.se>
---
I had to read config.c before I found the variable.
 Documentation/config.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index de9e72b..46f40ad 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -192,7 +192,7 @@ core.worktree::
 	variable and the '--work-tree' command line option.
 
 core.logAllRefUpdates::
-	Updates to a ref <ref> is logged to the file
+	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
-- 
1.5.3.rc5
Message 1 of 1 in “Add the word reflog to Documentation/config.txt:core.logAllRefUpdates”
  1. Add the word reflog to Documentation/config.txt:core.logAllRefUpdatesLukas Sandström, Aug 19, 2007

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.