From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Git Mailing List <git@vger.kernel.org>
Subject: [PATCH] Short-circuit git-clone-pack while cloning locally (take 2).
Date: Wed, 06 Jul 2005 13:04:21 -0700 [thread overview]
Message-ID: <7vd5pvwvju.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.58.0507060911510.3570@g5.osdl.org
When we are cloning a repository on a local filesystem, it is
faster to just create a hard linkfarm of .git/object hierarchy
and copy the .git/refs files. By default, the script uses the
clone-pack method, but it can be told with the -l flag to do the
hard linkfarm (falling back on recursive file copy) to replicate
the .git/object hierarchy.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
git-clone-script | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 files changed, 67 insertions(+), 1 deletions(-)
2bff57b39b9fd13b1319d0192e2a887eb82fa189
diff --git a/git-clone-script b/git-clone-script
--- a/git-clone-script
+++ b/git-clone-script
@@ -1,4 +1,70 @@
#!/bin/sh
+#
+# Copyright (c) 2005, Linus Torvalds
+# Copyright (c) 2005, Junio C Hamano
+#
+# Clone a repository into a different directory that does not yet exist.
+
+usage() {
+ echo >&2 "* git clone [-l] <repo> <dir>"
+ exit 1
+}
+
+use_local=no
+while
+ case "$#,$1" in
+ 0,*) break ;;
+ *,-l|*,--l|*,--lo|*,--loc|*,--loca|*,--local) use_local=yes ;;
+ *,-*) usage ;;
+ *) break ;;
+ esac
+do
+ shift
+done
+
repo="$1"
dir="$2"
-mkdir "$dir" && cd "$dir" && git-init-db && git-clone-pack "$repo"
+mkdir "$dir" &&
+D=$(
+ (cd "$dir" && git-init-db && pwd)
+) &&
+test -d "$D" || usage
+
+# We do local magic only when the user tells us to.
+case "$use_local" in
+yes)
+ ( cd "$repo/objects" ) || {
+ repo="$repo/.git"
+ ( cd "$repo/objects" ) || {
+ echo >&2 "-l flag seen but $repo is not local."
+ exit 1
+ }
+ }
+
+ # See if we can hardlink and drop "l" if not.
+ sample_file=$(cd "$repo" && \
+ find objects -type f -print | sed -e 1q)
+
+ # objects directory should not be empty since we are cloning!
+ test -f "$repo/$sample_file" || exit
+
+ l=
+ if ln "$repo/$sample_file" "$D/.git/objects/sample" 2>/dev/null
+ then
+ l=l
+ fi &&
+ rm -f "$D/.git/objects/sample" &&
+ cp -r$l "$repo/objects" "$D/.git/" || exit 1
+
+ # Make a duplicate of refs and HEAD pointer
+ HEAD=
+ if test -f "$repo/HEAD"
+ then
+ HEAD=HEAD
+ fi
+ tar Ccf "$repo" - refs $HEAD | tar Cxf "$D/.git" - || exit 1
+ exit 0
+ ;;
+esac
+
+cd "$D" && git clone-pack "$repo"
prev parent reply other threads:[~2005-07-07 1:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 19:57 expensive local git clone David S. Miller
2005-07-04 20:39 ` Linus Torvalds
2005-07-04 20:42 ` Petr Baudis
2005-07-04 21:00 ` David S. Miller
2005-07-04 21:40 ` Junio C Hamano
2005-07-04 22:49 ` David S. Miller
2005-07-04 23:07 ` Junio C Hamano
2005-07-04 21:44 ` Linus Torvalds
2005-07-05 20:17 ` [PATCH] Short-cut git-fetch-pack while cloning locally Junio C Hamano
2005-07-06 0:42 ` expensive local git clone Linus Torvalds
2005-07-06 8:14 ` [PATCH] Short-circuit git-clone-pack while cloning locally Junio C Hamano
2005-07-06 16:13 ` Linus Torvalds
2005-07-06 18:00 ` Junio C Hamano
2005-07-06 20:04 ` Junio C Hamano [this message]
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=7vd5pvwvju.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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