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

[RFH] git cherry-pick takes forever

From
MVMichal Vitecek <fuf@mageo.cz>
Date
Sep 10, 2008, 08:26 UTC
Message-ID
<20080910082610.GA3144@mageo.cz>
 Hello everyone,
 I have two git repositories: one is the origin of the other. However no
 merging is being done as the projects in the repositories quite differ
 but still use the same core. So to propagate changes I cherry-pick
 those which are useful from one repository to another.
 however 'git cherry-pick' has lately started to last almost forever:
 $ time git cherry-pick b42b77e66a83f1298d9900a9bb1078b9b42e8618
 Finished one cherry-pick.
 Created commit 7caef83: - removed some superfluous newlines
 2 files changed, 0 insertions(+), 2 deletions(-)
 git cherry-pick b42b77e66a83f1298d9900a9bb1078b9b42e8618  282.97s user 34.69s system 100% cpu 5:17.63 total
 Both repositories have approximately 16k commits and their forking
 point (merge base) is 250 to 490 commits far away. 'git gc' (even
 --prune) has been run.
 What can I do to make the 'git cherry-pick' instant again?
        Thank you,
 P.S.: I'm using git-1.6.0.1.
-- 
		Michal Vitecek		(fuf@mageo.cz)
Next: Junio C Hamano
Message 1 of 3 in “[RFH] git cherry-pick takes forever”
  1. Michal VitecekSep 10, 2008
  2. Junio C HamanoSep 10, 2008
  3. Michal VitecekSep 11, 2008

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.