[let's keep this on-list so others can benefit from the discussion] On Tue, May 15, 2012 at 12:38:59PM +0400, Dmitry Risenberg wrote: > > It's probably detecting renames as part of the merge, which can be > > expensive if the thing you are cherry-picking is far away from HEAD. You > > can try setting the merge.renamelimit config variable to something small > > (like 1; setting it to 0 means "no limit"). > > I set it to 1, but it didn't help at all - cherry-pick time is still > about the same. OK, then my guess was probably wrong. You'll have to try profiling (if you are on Linux, "perf record git cherry-pick ..."; perf report" is the simplest way). Or if the repository is publicly available, I can do a quick profile run. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html