From: Andreas Ericsson <ae@op5.se>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: git-merge performance
Date: Tue, 16 Oct 2007 19:34:10 +0200 [thread overview]
Message-ID: <4714F612.2010905@op5.se> (raw)
In-Reply-To: <20071016101748.ff132685.akpm@linux-foundation.org>
Andrew Morton wrote:
> My git-pulling script (git-1.4.2) seems to have got quite a bit slower
> since the post-2.6.23 patchflood. I just did a bit of poking and it's
> git-merge which is taking most of the time.
>
That's odd. If it had been the remote fetching it would have been
understandable. Is this also happening with more recent gits? I know there
are some significant performance-improvements in 1.5.3.4 (or below).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-10-16 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 17:17 git-merge performance Andrew Morton
2007-10-16 17:34 ` Andreas Ericsson [this message]
2007-10-16 18:18 ` Andrew Morton
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=4714F612.2010905@op5.se \
--to=ae@op5.se \
--cc=akpm@linux-foundation.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).