git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFH] send-pack: fix pipeline.
Date: Sun, 31 Dec 2006 11:56:11 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0612311155080.4473@woody.osdl.org> (raw)
In-Reply-To: <7v1wmgfm4s.fsf@assigned-by-dhcp.cox.net>



On Sun, 31 Dec 2006, Junio C Hamano wrote:
> 
> Thanks.  How about this?

Looks good to me. It should hopefully speed things up too, since now we 
don't need to first walk the whole object list and then _re-walk_ it when 
packing to get the size.

		Linus

      reply	other threads:[~2006-12-31 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-29 10:37 [PATCH/RFH] send-pack: fix pipeline Junio C Hamano
2006-12-29 20:13 ` Junio C Hamano
2006-12-29 21:20   ` Linus Torvalds
2006-12-29 23:53     ` Junio C Hamano
2007-01-02 14:06       ` Andy Whitcroft
2007-01-02 14:12         ` [PATCH] send pack check for failure to send revisions list Andy Whitcroft
2006-12-31  9:30     ` [PATCH/RFH] send-pack: fix pipeline Junio C Hamano
2006-12-31 19:56       ` Linus Torvalds [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=Pine.LNX.4.64.0612311155080.4473@woody.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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).