Junio C Hamano <gits...@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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to