From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org, Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Subject: Re: [PATCH] rebase [--onto O] A B: omit needless checkout
Date: Wed, 19 Mar 2008 12:19:49 -0700 [thread overview]
Message-ID: <7vhcf24j3e.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47E10D0D.2080702@viscovery.net> (Johannes Sixt's message of "Wed, 19 Mar 2008 13:54:37 +0100")
Johannes Sixt <j.sixt@viscovery.net> writes:
> Junio C Hamano schrieb:
>> This teaches "git rebase [--onto O] A B" to omit an unnecessary checkout
>> of branch B before it goes on.
>> ...
>
> This works for a frequent use-case of mine:
"Works" meaning "does not break", or "gives a great performance
improvement that it is worth having it early in a tagged release"?
> $ git rebase master devel
>
> where I am already on branch master, and now want to rebase devel on top
> of it.
>
> The code seems to take care of a lot of corner cases and less frequent
> use-cases, including using --onto, which I don't feel able to judge about.
>
>> +# git reset --hard "$onto^0"
>
> Don't forget to remove this line. ;)
next prev parent reply other threads:[~2008-03-19 19:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 19:10 optimized checkout+rebase? Ralf Wildenhues
2008-03-13 7:20 ` Johannes Sixt
2008-03-15 10:39 ` Ralf Wildenhues
2008-03-15 20:42 ` [PATCH] rebase [--onto O] A B: omit needless checkout Junio C Hamano
2008-03-15 22:21 ` Ralf Wildenhues
2008-03-16 3:56 ` Junio C Hamano
2008-03-19 12:54 ` Johannes Sixt
2008-03-19 19:19 ` Junio C Hamano [this message]
2008-03-20 7:41 ` Johannes Sixt
2008-03-20 7:53 ` Junio C Hamano
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=7vhcf24j3e.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.