From: Duy Nguyen <pclouds@gmail.com>
To: pawel.sikora@agmk.net
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: slow git-cherry-pick.
Date: Sun, 24 Nov 2013 19:47:10 +0700 [thread overview]
Message-ID: <CACsJy8CAAov1nSGPx79U+md4xROsCydidHPcipOb_sdFwNdSkA@mail.gmail.com> (raw)
In-Reply-To: <2142926.gg3W3MsbJZ@localhost.localdomain>
On Sun, Nov 24, 2013 at 5:45 PM, Paweł Sikora <pawel.sikora@agmk.net> wrote:
> i've recently reinstalled a fresh system (fc20-beta) on my workstation
> and observing a big slowdown on git cherry-pick operation (git-1.8.4.2-1).
> the previous centos installation with an old git version works faster
> (few seconds per cherry pick). now the same operation takes >1 min.
What is the git version the reinstallation? Do you cherry-pick on one
commit or a commit range?
--
Duy
next prev parent reply other threads:[~2013-11-24 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 10:45 slow git-cherry-pick Paweł Sikora
2013-11-24 12:47 ` Duy Nguyen [this message]
2013-11-24 12:48 ` Duy Nguyen
2013-11-24 19:17 ` Paweł Sikora
2013-11-25 17:26 ` Junio C Hamano
2013-12-03 19:31 ` Paweł Sikora
2013-12-03 20:13 ` Thomas Rast
2013-12-04 1:07 ` Duy Nguyen
2013-12-04 12:46 ` Paweł Sikora
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=CACsJy8CAAov1nSGPx79U+md4xROsCydidHPcipOb_sdFwNdSkA@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=pawel.sikora@agmk.net \
/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).