From: "Shawn O. Pearce" <spearce@spearce.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Jason Merrill <jason@redhat.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
git@vger.kernel.org, Hin-Tak Leung <hintak.leung@gmail.com>
Subject: Re: [PATCH] make 'git clone' ask the remote only for objects it cares about
Date: Sat, 26 Sep 2009 12:50:39 -0700 [thread overview]
Message-ID: <20090926195039.GG14660@spearce.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0909252314260.4997@xanadu.home>
Nicolas Pitre <nico@fluxnic.net> wrote:
> Current behavior of 'git clone' when not using --mirror is to fetch
> everything from the peer, and then filter out unwanted refs just before
> writing them out to the cloned repository. This may become highly
> inefficient if the peer has an unusual ref namespace, or if it simply
> has "remotes" refs of its own, and those locally unwanted refs are
> connecting to a large set of objects which becomes unreferenced as soon
> as they are fetched.
...
> +static void write_remote_refs(const struct ref *local_refs, const char *reflog)
Here reflog is now unused. I'm going to squash this in.
diff --git a/builtin-clone.c b/builtin-clone.c
index edf7c7f..4992c25 100644
--- a/builtin-clone.c
+++ b/builtin-clone.c
@@ -342,7 +342,7 @@ static struct ref *wanted_peer_refs(const struct ref *refs,
return local_refs;
}
-static void write_remote_refs(const struct ref *local_refs, const char *reflog)
+static void write_remote_refs(const struct ref *local_refs)
{
const struct ref *r;
@@ -534,7 +534,7 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
if (refs) {
clear_extra_refs();
- write_remote_refs(mapped_refs, reflog_msg.buf);
+ write_remote_refs(mapped_refs);
remote_head = find_ref_by_name(refs, "HEAD");
remote_head_points_at =
--
Shawn.
next prev parent reply other threads:[~2009-09-26 19:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 1:11 git gc expanding packed data? Andreas Schwab
2009-08-08 13:05 ` Hin-Tak Leung
2009-08-08 13:25 ` Andreas Schwab
2009-08-09 2:56 ` Nicolas Pitre
2009-08-09 7:43 ` Andreas Schwab
2009-09-25 18:05 ` git clone sending unneeded objects (was : git gc expanding packed data?) Jason Merrill
2009-09-25 19:34 ` git clone sending unneeded objects Matthieu Moy
2009-09-25 19:43 ` Jason Merrill
2009-09-25 19:53 ` Nicolas Pitre
2009-09-25 20:20 ` Jason Merrill
2009-09-25 20:47 ` Nicolas Pitre
2009-09-25 23:17 ` Jason Merrill
2009-09-26 0:49 ` Nicolas Pitre
2009-09-26 3:54 ` [PATCH] make 'git clone' ask the remote only for objects it cares about Nicolas Pitre
2009-09-26 7:21 ` Andreas Schwab
2009-09-26 19:50 ` Shawn O. Pearce [this message]
2009-09-27 0:26 ` Nicolas Pitre
2009-09-26 4:44 ` git clone sending unneeded objects Jason Merrill
2009-09-26 13:33 ` Jason Merrill
2009-09-27 2:26 ` Nicolas Pitre
2009-09-27 1:27 ` Nicolas Pitre
2009-09-27 2:04 ` Shawn O. Pearce
2009-09-27 2:31 ` Nicolas Pitre
2009-09-27 4:35 ` Jason Merrill
2009-09-28 4:18 ` Nicolas Pitre
2009-09-26 0:43 ` Hin-Tak Leung
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=20090926195039.GG14660@spearce.org \
--to=spearce@spearce.org \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hintak.leung@gmail.com \
--cc=jason@redhat.com \
--cc=nico@fluxnic.net \
/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).