From: Jeff King <peff@peff.net>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Eugene Sajine <euguess@gmail.com>,
git@vger.kernel.org
Subject: Re: [BUG] - git rebase -i performs rebase when it shouldn't?
Date: Sun, 11 Apr 2010 06:15:26 -0400 [thread overview]
Message-ID: <20100411101526.GA20484@coredump.intra.peff.net> (raw)
In-Reply-To: <4BC0D87E.70001@kdbg.org>
On Sat, Apr 10, 2010 at 09:58:54PM +0200, Johannes Sixt wrote:
> > git checkout foo&& git rebase master
> > git checkout bar&& git rebase master
> > git checkout baz&& git rebase master
>
> I'm actually very glad that the current interface is the way it is -
> because it can do the rebase *without* the checkout. This way you can
> save a lot of recompilation due to changed timestamps if the topic is
> based on an old version.
>
> Only that some (all?) variants of rebase still unnecessarily do the
> checkout...
Good point. Originally, we did the rebase directly on the branch, though
I'm not sure if we did "checkout $branch && reset $onto" or "branch -f
$branch $onto && checkout $branch". These days we operate on a detached
HEAD, and we seem to "checkout $onto^0", which should do the
optimization you mention.
-Peff
next prev parent reply other threads:[~2010-04-11 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 19:35 [BUG] - git rebase -i performs rebase when it shouldn't? Eugene Sajine
2010-04-10 4:26 ` Jeff King
2010-04-10 4:39 ` Junio C Hamano
2010-04-10 4:47 ` Jeff King
2010-04-10 19:58 ` Johannes Sixt
2010-04-11 10:15 ` Jeff King [this message]
2010-04-11 17:54 ` Johannes Sixt
2010-04-12 1:01 ` Jeff King
2010-04-12 10:50 ` Michal Vitecek
2010-04-12 17:39 ` Johannes Sixt
2010-04-10 22:10 ` Eugene Sajine
2010-04-11 10:22 ` Jeff King
2010-04-11 14:06 ` Eugene Sajine
2010-04-12 14:09 ` Eugene Sajine
2010-04-12 15:13 ` Johannes Sixt
2010-04-12 15:28 ` Eugene Sajine
2010-04-12 15:47 ` Johannes Sixt
2010-04-13 16:30 ` Eugene Sajine
2010-04-14 6:08 ` Johannes Sixt
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=20100411101526.GA20484@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.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).