From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH] git init: activate rerere by default
Date: Thu, 5 Jul 2007 13:16:02 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707051312260.9789@racer.site> (raw)
We have a working implementation of rerere since long ago, and we even
make sure that it works as expected in a test case. It is also a very
useful feature, so why not turn it on for the benefit of users who are
not even aware of it? This patch does that.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
Maybe it is too late for 1.5.3? But maybe this is nice enough to
have in 1.5.3?
BTW I shamelessly put in a comment to boost my comment ration on
ohloh.net...
builtin-init-db.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/builtin-init-db.c b/builtin-init-db.c
index 66ddaeb..aa3a01e 100644
--- a/builtin-init-db.c
+++ b/builtin-init-db.c
@@ -293,6 +293,9 @@ static int create_default_files(const char *git_dir, const char *git_work_tree,
if (git_work_tree)
git_config_set("core.worktree", git_work_tree);
}
+ /* activate rerere */
+ strcpy(path + len, "rr-cache");
+ safe_create_dir(path, 1);
return reinit;
}
--
1.5.3.rc0.2689.g99ca2-dirty
next reply other threads:[~2007-07-05 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 12:16 Johannes Schindelin [this message]
2007-07-05 13:10 ` [PATCH] git init: activate rerere by default Alex Riesen
2007-07-05 16:46 ` Junio C Hamano
2007-07-05 17:15 ` Johannes Schindelin
2007-07-05 18:53 ` Junio C Hamano
2007-07-05 19:22 ` Johannes Schindelin
2007-07-05 21:40 ` Alex Riesen
2007-07-05 22:29 ` Johannes Schindelin
2007-07-06 5:12 ` Junio C Hamano
2007-07-06 12:03 ` Johannes Schindelin
2007-07-06 11:12 ` しらいしななこ
[not found] <200707061112.l66BCb6w017186@mi1.bluebottle.com>
2007-07-06 12:03 ` Johannes Schindelin
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=Pine.LNX.4.64.0707051312260.9789@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).