git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Kumria <wildfire@progsoc.org>
To: git@vger.kernel.org
Cc: Anand Kumria <wildfire@progsoc.org>
Subject: [PATCH]  Make logAllRefUpdates true by default
Date: Mon, 27 Nov 2006 02:36:43 +1100	[thread overview]
Message-ID: <11645554033331-git-send-email-wildfire@progsoc.org> (raw)

reflog support, which allows you to determine what the state of a branch
was at a particular date/time, is often cited as something that would be
useful to have on by default.  Modify git init-db, so that newly created
repositories have this on.

Signed-off-by: Anand Kumria <wildfire@progsoc.org>
---
 Documentation/config.txt |    2 +-
 builtin-init-db.c        |    3 +++
 2 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index 9d3c71c..e8d0bc1 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -80,7 +80,7 @@ core.logAllRefUpdates::
 
 	This information can be used to determine what commit
 	was the tip of a branch "2 days ago".  This value is
-	false by default (no automated creation of log files).
+	true by default.
 
 core.repositoryFormatVersion::
 	Internal variable identifying the repository format and layout
diff --git a/builtin-init-db.c b/builtin-init-db.c
index 235a0ee..4ea865d 100644
--- a/builtin-init-db.c
+++ b/builtin-init-db.c
@@ -239,6 +239,9 @@ static void create_default_files(const c
 		git_config_set("core.filemode",
 			       filemode ? "true" : "false");
 	}
+
+	git_config_set("core.logAllRefUpdates", "true");
+
 }
 
 static const char init_db_usage[] =
-- 
1.4.3.3

             reply	other threads:[~2006-11-26 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 15:36 Anand Kumria [this message]
2006-11-26 20:12 ` [PATCH] Make logAllRefUpdates true by default Junio C Hamano
2006-11-26 23:05   ` Horst H. von Brand
2006-11-27  5:01   ` Shawn Pearce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11645554033331-git-send-email-wildfire@progsoc.org \
    --to=wildfire@progsoc.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).