From: Nick Andrew <nick@nick-andrew.net>
To: Csaba Henk <csaba-ml@creo.hu>
Cc: git@vger.kernel.org
Subject: Re: Is rebase always destructive?
Date: Mon, 1 Dec 2008 23:11:40 +1100 [thread overview]
Message-ID: <20081201121140.GB32415@mail.local.tull.net> (raw)
In-Reply-To: <slrngj7jch.2srb.csaba-ml@beastie.creo.hu>
On Mon, Dec 01, 2008 at 11:41:39AM +0000, Csaba Henk wrote:
> When doing a rebase, I can find a number of reasons for which one might
> feel like to preserve the rebased branch (that is, perform an operation
> which copies the branch over a new base, not moves).
[...]
> I can't see any option for rebase which would yield this cp-like
> behaviour. Am I missing something?
How about this:
git checkout topic
git branch keepme
git rebase master
Your 'topic' branch will now be rebased against master, and due
to the 'keepme' branch pointer at the original topic HEAD, you can
see the original commits before rebasing.
Nick.
next prev parent reply other threads:[~2008-12-01 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 11:41 Is rebase always destructive? Csaba Henk
2008-12-01 11:54 ` Johan Herland
2008-12-01 12:11 ` Nick Andrew [this message]
2008-12-01 17:37 ` Csaba Henk
2008-12-01 20:19 ` Robin Rosenberg
2008-12-01 16:45 ` Andreas Ericsson
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=20081201121140.GB32415@mail.local.tull.net \
--to=nick@nick-andrew.net \
--cc=csaba-ml@creo.hu \
--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).