From: linux@horizon.com
To: git@vger.kernel.org
Subject: How to do a reverse rebase?
Date: 20 Aug 2007 01:32:37 -0400 [thread overview]
Message-ID: <20070820053237.9349.qmail@science.horizon.com> (raw)
Okay, this is picayune whining, but when you've fixed all the big
bugs...
I don't want to rebase HEAD on *that*, but rather rebase *that*
on top of the current HEAD.
Sometimes I have a little debug hack on a branch by itself, and I
discover that I need it again, so I want to rebase it on top of
current development.
But there's been a LOT of development in the meantime. And if I do
git-rebase HEAD debug_hack
git first checks out debug_hack. This takes a while and, more
importantly, every file modified in HEAD...debug_hack has its timestamp
touched and make(1) insists on recompiling it.
I want to only modify the three files that are touched on the debug_hack
branch, so my recompile times aren't too long.
Currently, when I remember, I'll use git-cherry-pick and manually
rename branches.
Is there an easier way? Or should I just learn StGit?
next reply other threads:[~2007-08-20 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 5:32 linux [this message]
2007-08-20 5:58 ` How to do a reverse rebase? Shawn O. Pearce
2007-08-20 6:33 ` Junio C Hamano
2007-08-20 10:39 ` linux
2007-08-20 9:49 ` 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=20070820053237.9349.qmail@science.horizon.com \
--to=linux@horizon.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).