From: Jay Soffian <jaysoffian@gmail.com>
To: git <git@vger.kernel.org>
Subject: rebase vs rebase -i
Date: Wed, 3 Feb 2010 23:19:24 -0500 [thread overview]
Message-ID: <76718491002032019i5f8ea947paa527988ddb7a378@mail.gmail.com> (raw)
Why does git rebase use format-patch + am, while rebase -i uses cherry-pick?
Just curious. In particular though, it seems especially odd in this case:
$ git rebase --onto <newbase> <upstream>
vs
$ env GIT_EDITOR=true git rebase -i --onto <newbase> <upstream>
Both in theory produce an identical end-result, while using two
different implementations.
(Here I'm setting GIT_EDITOR=true just to demonstrate that I didn't
change the list of commits in the latter case.)
j.
next reply other threads:[~2010-02-04 4:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 4:19 Jay Soffian [this message]
2010-02-04 13:27 ` rebase vs rebase -i Johannes Schindelin
2010-02-04 17:14 ` Jay Soffian
2010-02-04 18:00 ` Johannes Schindelin
2010-02-04 18:10 ` Jay Soffian
2010-02-04 18:46 ` Johannes Schindelin
2010-02-04 19:57 ` Jay Soffian
2010-02-05 0:45 ` Junio C Hamano
2010-02-05 1:18 ` Junio C Hamano
2010-02-05 1:20 ` Jay Soffian
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=76718491002032019i5f8ea947paa527988ddb7a378@mail.gmail.com \
--to=jaysoffian@gmail.com \
--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).