From: karsten.blees@dcon.de
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, msysgit@googlegroups.com, pro-logic@optusnet.com.au
Subject: Re: [PATCH] update-index/diff-index: use core.preloadindex to improve performance
Date: Tue, 13 Nov 2012 16:36:06 +0100 [thread overview]
Message-ID: <OF27D0F811.18A373FB-ONC1257AB5.0055809D-C1257AB5.0055B47D@dcon.de> (raw)
In-Reply-To: <20121102153800.GE11170@sigill.intra.peff.net>
Jeff King <peff@peff.net> wrote on 02.11.2012 16:38:00:
> On Fri, Nov 02, 2012 at 11:26:16AM -0400, Jeff King wrote:
>
> > Still, I don't think we need to worry about performance regressions,
> > because people who don't have a setup suitable for it will not turn on
> > core.preloadindex in the first place. And if they have it on, the more
> > places we use it, probably the better.
>
> BTW, your patch was badly damaged in transit (wrapped, and tabs
> converted to spaces). I was able to fix it up, but please check your
> mailer's settings.
>
Yes, I feared as much, that's why I included the pull URL (the company MTA
only accepts outbound mail from Notes clients, sorry).
Is there a policy for people with broken mailers (send patch as
attachment, add pull URL more prominently, don't include plaintext patch
at all...)?
next prev parent reply other threads:[~2012-11-13 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 9:50 [PATCH] update-index/diff-index: use core.preloadindex to improve performance karsten.blees
2012-10-30 10:15 ` Erik Faye-Lund
2012-10-30 22:50 ` Albert Krawczyk
2012-11-02 15:26 ` Jeff King
2012-11-02 15:38 ` Jeff King
2012-11-13 15:36 ` karsten.blees [this message]
2012-11-13 16:46 ` Junio C Hamano
2012-11-13 21:51 ` Karsten Blees
2012-11-13 15:33 ` karsten.blees
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF27D0F811.18A373FB-ONC1257AB5.0055809D-C1257AB5.0055B47D@dcon.de \
--to=karsten.blees@dcon.de \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
--cc=peff@peff.net \
--cc=pro-logic@optusnet.com.au \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).