git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Reduce the number of connects when fetching
Date: Mon, 04 Feb 2008 19:09:45 -0800	[thread overview]
Message-ID: <7v8x20gkue.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: alpine.LNX.1.00.0802041323450.13593@iabervon.org

Daniel Barkalow <barkalow@iabervon.org> writes:

> This shares the connection between getting the remote ref list and
> getting objects in the first batch. (A second connection is still used
> to follow tags)
> ---

No signoff.

> There's a bug here, fixed in the next patch, but it's just cosmetic (we 
> hang up on the remote end unexpectedly if we turn out not to need 
> anything), and I think reorganizing changes to not do that makes the 
> changes harder to follow.

> @@ -706,9 +703,34 @@ int cmd_fetch_pack(int argc, const char **argv, const char *prefix)
>  	if (!dest)
>  		usage(fetch_pack_usage);
>  
> -	ref = fetch_pack(&args, dest, nr_heads, heads, NULL);
> +	int fd[2];
> +	struct child_process *conn = git_connect(fd, (char *)dest, args.uploadpack,
> +                          args.verbose ? CONNECT_VERBOSE : 0);

Decl after statement.

But other than that, good job.  I did not realize it would be
doable this cleanly.

Will squash all three and queue for 'next'.

  reply	other threads:[~2008-02-05  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 18:26 [PATCH 1/2] Reduce the number of connects when fetching Daniel Barkalow
2008-02-05  3:09 ` Junio C Hamano [this message]
2008-02-05 19:20   ` Daniel Barkalow

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=7v8x20gkue.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.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).