git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git pull takes ~8 seconds on up-to-date Linux git tree

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 4, 2012, 20:44 UTC
Message-ID
<7v8vbmx90p.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7vhaqaxawh.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 13 quoted lines
> 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.

Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 13 in “git pull takes ~8 seconds on up-to-date Linux git tree”
  1. Markus TrippelsdorfOct 4, 2012
  2. Jeff KingOct 4, 2012
  3. Markus TrippelsdorfOct 4, 2012
  4. Junio C HamanoOct 4, 2012
  5. Junio C HamanoOct 4, 2012
  6. Junio C HamanoOct 4, 2012
  7. Junio C HamanoOct 4, 2012
  8. Junio C HamanoOct 4, 2012
  9. Junio C HamanoOct 4, 2012
  10. Junio C HamanoOct 5, 2012
  11. Jeff KingOct 5, 2012
  12. Junio C HamanoOct 6, 2012
  13. Jeff KingOct 6, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.