From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
git@vger.kernel.org, git-dev@github.com
Subject: Re: [PATCH] fetch: avoid quadratic loop checking for updated submodules
Date: Mon, 12 Sep 2011 19:25:19 -0400 [thread overview]
Message-ID: <20110912232519.GA30020@sigill.intra.peff.net> (raw)
In-Reply-To: <7vboup4azh.fsf@alter.siamese.dyndns.org>
On Mon, Sep 12, 2011 at 04:06:10PM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > Also also. I was a little turned off by the fact that every fetch is
> > going to do the equivalent of "git log --raw -m $new --not $old",
> > whether you have submodules or not.
>
> Notice I called your patch solving "the other half"?
> See http://thread.gmane.org/gmane.comp.version-control.git/181101
Oh, heh. I totally missed that thread. I don't usually pay attention to
submodule patches, and came at this completely from the "why is git
fetch so slow" angle. Glad to see Jens and I are meeting in the middle.
:)
-Peff
next prev parent reply other threads:[~2011-09-12 23:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 19:56 [PATCH] fetch: avoid quadratic loop checking for updated submodules Jeff King
2011-09-12 20:21 ` Junio C Hamano
2011-09-13 19:34 ` Jens Lehmann
2011-09-14 18:26 ` Jens Lehmann
2011-09-12 21:25 ` Junio C Hamano
2011-09-12 22:49 ` Jeff King
2011-09-12 23:06 ` Junio C Hamano
2011-09-12 23:25 ` Jeff King [this message]
2011-09-12 23:33 ` Junio C Hamano
2011-09-13 19:13 ` Jens Lehmann
2011-09-13 22:17 ` Jeff King
2011-09-14 13:20 ` Marc Branchaud
2011-09-14 18:27 ` Jens Lehmann
2011-09-14 18:29 ` Jeff King
2011-09-13 16:40 ` Christian Couder
2011-09-13 17:15 ` Jeff King
2011-09-13 17:34 ` 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=20110912232519.GA30020@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Jens.Lehmann@web.de \
--cc=git-dev@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).