From: Junio C Hamano <junkio@cox.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: expensive local git clone
Date: Mon, 04 Jul 2005 14:40:11 -0700 [thread overview]
Message-ID: <7v7jg6i72c.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050704.140043.112609056.davem@davemloft.net> (David S. Miller's message of "Mon, 04 Jul 2005 14:00:43 -0700 (PDT)")
>>>>> "DSM" == David S Miller <davem@davemloft.net> writes:
DSM> I keep hoping git-clone-script is going to be a good way
DSM> to clone two local trees. Is my hope misguided? :-)
Something along these lines?
------------
Short-cut "git fetch" when cloning locally.
Instead of calling local-pull to "do the right thing", just
hardlink or copy the object files over when we know we are doing
the clone locally.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
cd /opt/packrat/playpen/public/in-place/git/git.junio/
jit-diff
# - master: git-format-patch: Prepare patches for e-mail submission.
# + (working tree)
diff --git a/git-clone-script b/git-clone-script
--- a/git-clone-script
+++ b/git-clone-script
@@ -1,7 +1,39 @@
#!/bin/sh
repo="$1"
dir="$2"
-mkdir $dir || exit 1
-cd $dir
-git-init-db
-git fetch "$repo" && ( git-rev-parse FETCH_HEAD > .git/HEAD )
+mkdir "$dir" &&
+D=$(
+ (cd "$dir" && git-init-db && pwd)
+) || exit 1
+
+# See if repo is a local directory.
+if (
+ cd "$repo/objects" 2>/dev/null
+)
+then
+ # 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
+
+ if ln "$repo/$sample_file" "$D/.git/objects/sample" 2>/dev/null
+ then
+ l=l
+ else
+ l=
+ fi &&
+ rm -f "$D/.git/objects/sample" &&
+
+ cd "$repo" &&
+ find objects -type f -print |
+ cpio -puam$l "$D/.git" || exit 1
+
+ # FETCH_HEAD is always HEAD because we do not do the
+ # extra parameter to "git fetch".
+ pwd
+ cat "HEAD" >"$D/.git/FETCH_HEAD"
+ cd "$D"
+else
+ cd "$D" && git fetch "$repo"
+fi && ( git-rev-parse FETCH_HEAD > .git/HEAD )
Compilation finished at Mon Jul 4 14:37:29
next prev parent reply other threads:[~2005-07-04 21:41 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 [this message]
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 ` [PATCH] Short-circuit git-clone-pack while cloning locally (take 2) Junio C Hamano
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=7v7jg6i72c.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