From: Junio C Hamano <gitster@pobox.com>
To: Ivan Todoroski <grnch@gmx.net>
Cc: Jeff King <peff@peff.net>, Shawn Pearce <spearce@spearce.org>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH/RFC v2 2/4] remote-curl: send the refs to fetch-pack on stdin
Date: Tue, 27 Mar 2012 10:18:04 -0700 [thread overview]
Message-ID: <7v8vimj73n.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4F715D91.5070901@gmx.net> (Ivan Todoroski's message of "Tue, 27 Mar 2012 08:26:25 +0200")
Ivan Todoroski <grnch@gmx.net> writes:
> If a remote repo has too many tags (or branches), cloning it over the
> smart HTTP transport can fail because remote-curl.c puts all the refs
> from the remote repo on the fetch-pack command line. This can make the
> command line longer than the global OS command line limit, causing
> fetch-pack to fail.
>
> This is especially a problem on Windows where the command line limit is
> orders of magnitude shorter than Linux. There are already real repos out
> there that msysGit cannot clone over smart HTTP due to this problem.
>
> To solve this problem we teach remote-curl.c to pipe the refs to
> fetch-pack using the new --stdin option, instead of on the fetch-pack
> command line.
>
> For a more detailed discussion of the problem see the parent of this
> commit, titled "fetch-pack: new --stdin option to read refs from stdin".
Thanks. As there is no way for this single commit to be applied without
the previous step, you could have just said:
Now we can throw arbitrary number of refs at fetch-pack using
its --stdin option, use it in remote-curl helper to lift the
command line length limit.
or something ;-).
> @@ -626,6 +630,7 @@ static int fetch_git(struct discovery *heads,
> int nr_heads, struct ref **to_fetch)
> {
> struct rpc_state rpc;
> + struct strbuf preamble;
> char *depth_arg = NULL;
> const char **argv;
> int argc = 0, i, err;
> @@ -633,6 +638,7 @@ static int fetch_git(struct discovery *heads,
> argv = xmalloc((15 + nr_heads) * sizeof(char*));
> argv[argc++] = "fetch-pack";
> argv[argc++] = "--stateless-rpc";
> + argv[argc++] = "--stdin";
> argv[argc++] = "--lock-pack";
> if (options.followtags)
> argv[argc++] = "--include-tag";
> @@ -651,23 +657,28 @@ static int fetch_git(struct discovery *heads,
> argv[argc++] = depth_arg;
> }
> argv[argc++] = url;
> + argv[argc++] = NULL;
> +
> + strbuf_init(&preamble, 4);
Curious.
If "4" does not really matter, I would drop this and use STRBUF_INIT at
the beginning instead.
> for (i = 0; i < nr_heads; i++) {
> struct ref *ref = to_fetch[i];
> if (!ref->name || !*ref->name)
> die("cannot fetch by sha1 over smart http");
> - argv[argc++] = ref->name;
> + packet_buf_write(&preamble, "%s\n", ref->name);
> }
> - argv[argc++] = NULL;
> + packet_buf_flush(&preamble);
>
> memset(&rpc, 0, sizeof(rpc));
> rpc.service_name = "git-upload-pack",
> rpc.argv = argv;
> + rpc.stdin_preamble = &preamble;
> rpc.gzip_request = 1;
>
> err = rpc_service(&rpc, heads);
> if (rpc.result.len)
> safe_write(1, rpc.result.buf, rpc.result.len);
> strbuf_release(&rpc.result);
> + strbuf_release(&preamble);
> free(argv);
> free(depth_arg);
> return err;
next prev parent reply other threads:[~2012-03-27 17:18 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 8:14 Clone fails on a repo with too many heads/tags Ivan Todoroski
2012-03-18 11:37 ` Ivan Todoroski
2012-03-18 12:04 ` Nguyen Thai Ngoc Duy
2012-03-18 16:36 ` Jakub Narebski
2012-03-18 19:07 ` Jeff King
2012-03-18 22:07 ` Jakub Narebski
2012-03-19 2:32 ` Jeff King
2012-03-19 2:43 ` Nguyen Thai Ngoc Duy
2012-03-19 2:45 ` Jeff King
2012-03-19 1:05 ` Ivan Todoroski
2012-03-19 1:30 ` Nguyen Thai Ngoc Duy
2012-03-19 2:44 ` Jeff King
2012-03-21 11:05 ` Ivan Todoroski
2012-03-21 14:28 ` Shawn Pearce
2012-03-21 17:14 ` Jeff King
2012-03-21 17:59 ` Jakub Narebski
2012-03-21 20:02 ` Ivan Todoroski
2012-03-21 20:17 ` Jeff King
2012-03-24 20:49 ` Ivan Todoroski
2012-03-25 1:06 ` Jeff King
2012-03-25 2:32 ` Jeff King
2012-03-25 17:33 ` Ivan Todoroski
2012-03-25 17:54 ` Ivan Todoroski
2012-03-26 17:33 ` Jeff King
2012-03-27 7:07 ` Ivan Todoroski
2012-03-25 15:30 ` Ivan Todoroski
2012-03-24 20:53 ` [PATCH/RFC 1/2] fetch-pack: new option to read refs from stdin Ivan Todoroski
2012-03-25 1:19 ` Jeff King
2012-03-25 9:39 ` Ivan Todoroski
2012-03-25 15:15 ` Ivan Todoroski
2012-03-25 20:00 ` Ivan Todoroski
2012-03-26 17:21 ` Jeff King
2012-03-26 17:49 ` Ivan Todoroski
2012-03-26 17:51 ` Jeff King
2012-03-24 20:54 ` [PATCH/RFC 2/2] remote-curl: send the refs to fetch-pack on stdin Ivan Todoroski
2012-03-25 1:24 ` Jeff King
2012-03-25 9:52 ` Ivan Todoroski
2012-03-26 17:24 ` Jeff King
2012-03-27 6:23 ` [PATCH/RFC v2 0/4] Fix fetch-pack command line overflow during clone Ivan Todoroski
2012-03-27 6:25 ` [PATCH/RFC v2 1/4] fetch-pack: new --stdin option to read refs from stdin Ivan Todoroski
2012-03-27 16:59 ` Junio C Hamano
2012-03-27 23:18 ` Ivan Todoroski
2012-03-27 23:26 ` Junio C Hamano
2012-03-27 23:48 ` Ivan Todoroski
2012-03-27 6:26 ` [PATCH/RFC v2 2/4] remote-curl: send the refs to fetch-pack on stdin Ivan Todoroski
2012-03-27 17:18 ` Junio C Hamano [this message]
2012-03-27 23:20 ` Ivan Todoroski
2012-03-27 6:27 ` [PATCH/RFC v2 3/4] fetch-pack: test cases for the new --stdin option Ivan Todoroski
2012-03-27 17:40 ` Junio C Hamano
2012-03-27 23:36 ` Ivan Todoroski
2012-03-27 23:43 ` Junio C Hamano
2012-03-28 0:14 ` Ivan Todoroski
2012-03-27 6:28 ` [PATCH/RFC v2 4/4] remote-curl: main test case for the OS command line overflow Ivan Todoroski
2012-03-27 17:43 ` 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=7v8vimj73n.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=grnch@gmx.net \
--cc=jnareb@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.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).