From: Michal Vitecek <fuf@mageo.cz>
To: git list <git@vger.kernel.org>
Subject: [RFH] git cherry-pick takes forever
Date: Wed, 10 Sep 2008 10:26:10 +0200 [thread overview]
Message-ID: <20080910082610.GA3144@mageo.cz> (raw)
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 reply other threads:[~2008-09-10 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 8:26 Michal Vitecek [this message]
2008-09-10 10:00 ` [RFH] git cherry-pick takes forever Junio C Hamano
2008-09-11 7:56 ` Michal Vitecek
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=20080910082610.GA3144@mageo.cz \
--to=fuf@mageo.cz \
--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).