From: Johannes Sixt <j.sixt@viscovery.net>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, git@vger.kernel.org
Subject: Re: optimized checkout+rebase?
Date: Thu, 13 Mar 2008 08:20:24 +0100 [thread overview]
Message-ID: <47D8D5B8.70809@viscovery.net> (raw)
In-Reply-To: <20080312191041.GF3198@ins.uni-bonn.de>
Ralf Wildenhues schrieb:
> this is a common work pattern:
>
> git checkout master
> git pull
> for branch in $my_topic_branches; do
> git checkout $branch
> git rebase master
> # occasional fixups here...
> done
>
> Now, it looks to me that one of the first operations of rebase just
> undoes part of the work that the checkout of the branch did. Well,
> "undoes" is the wrong word, what I mean is that it looks like work
> may be saved by combining the two checkout and the rewinding step.
Well, what you could do is:
for branch in $my_topic_branches; do
git rebase master $branch
# occasional fixups here...
done
But it seems that even then rebase first does the checkout $branch, and
then the checkout master right after that. At least the first checkout
should be unnecessary because all the revision range computations and
patch formating should be possible to do without the checkout. (The second
checkout is indispensable, of course.)
This has annoyed me, too, but not so much that I started looking at a fix,
though...
-- Hannes
next prev parent reply other threads:[~2008-03-13 7:21 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 [this message]
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
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=47D8D5B8.70809@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Ralf.Wildenhues@gmx.de \
--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).