From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Joshua Jensen <jjensen@workspacewhiz.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Stephen Bash <bash@genarts.com>
Subject: Re: Difference between 'git rebase' and 'git rebase -m'
Date: Wed, 17 Nov 2010 21:38:38 +0700 [thread overview]
Message-ID: <AANLkTikY0BE-PMP5TpAjL2TOYBQ-sTAAka2Gt6f8qd3P@mail.gmail.com> (raw)
In-Reply-To: <4CE3DA66.80808@drmicha.warpmail.net>
On Wed, Nov 17, 2010 at 8:36 PM, Michael J Gruber
<git@drmicha.warpmail.net> wrote:
> Nguyen Thai Ngoc Duy venit, vidit, dixit 17.11.2010 12:43:
>> On Wed, Nov 17, 2010 at 1:27 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>>> Joshua Jensen wrote:
>>>
>>>> I'm curious as to why 'git rebase -m' isn't the default and what the
>>>> real difference is between 'git rebase' and 'git rebase -m'.
>>>
>>> git rebase is faster. :)
>>
>> Perhaps a config option to let people to default to -m. Or perhaps
>> they can just make an alias.
>>
>> By the way, can we make rebase even faster? Rebasing ~20 patches or
>> more seems slow to me. I don't know much how patching works though.
>
> git sequencer...
Sequencer is definitely an improvement. But does it improve
performance? I don't know rebase internals but I think that it needs
to update worktree/index for every commit, which might slow things
down a bit.
--
Duy
prev parent reply other threads:[~2010-11-17 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 17:35 Difference between 'git rebase' and 'git rebase -m' Joshua Jensen
2010-11-16 18:27 ` Jonathan Nieder
2010-11-17 11:43 ` Nguyen Thai Ngoc Duy
2010-11-17 13:36 ` Michael J Gruber
2010-11-17 14:38 ` Nguyen Thai Ngoc Duy [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=AANLkTikY0BE-PMP5TpAjL2TOYBQ-sTAAka2Gt6f8qd3P@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=bash@genarts.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.com \
--cc=jrnieder@gmail.com \
/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).