From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 04 Oct 2012 20:44:06 GMT
Subject: Re: git pull takes ~8 seconds on up-to-date Linux git tree
Message-ID: <7v8vbmx90p.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7vhaqaxawh.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

> It gets more curious, though.
> ...
> However.
>
> If I revert 5802f81 that updated the implementation of fmt-merge-msg
> on top of 'master', *without* reverting 34f5130^2, I get ~4.5 seconds.
> As we are doing an "Already up-to-date" pull, I thought there is no
> need to call fmt-merge-msg in the first place?
>
> Which may indicate that "git merge" has been broken for a long time
> and making unnecessary calls.
>
> Hrmmm...

Actually there is nothing curious about this.  "git pull" prepares
the merge message before it calls "git rebase" or "git merge", and
there is no fast-path that detects "Already up-to-date" in it.