git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org
Subject: Re: git rebase -i slow for a reason ?
Date: Thu, 15 Apr 2010 10:20:09 +0530	[thread overview]
Message-ID: <w2jf3271551004142150yc0323559x7dd66da56f473d22@mail.gmail.com> (raw)
In-Reply-To: <20100413100435.GA7441@glandium.org>

Hi,

> Most of the time, I run git rebase with -i, so while it is slow, I
> always assumed there was somehow a reason.

Technically, the interactive counterpart is simply a shell script that
calls the git-rebase binary along with a bunch of other things. See
git-rebase--interactive in the the source tree. Your observations
about speed mainly have to do with how the interactive counterpart
recursively cherry-picks and rebases.

-- Ram

      reply	other threads:[~2010-04-15  4:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 10:04 git rebase -i slow for a reason ? Mike Hommey
2010-04-15  4:50 ` Ramkumar Ramachandra [this message]

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=w2jf3271551004142150yc0323559x7dd66da56f473d22@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mh@glandium.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).