From: "Stefan Schulze" <algroth@gmx.de>
To: <git@vger.kernel.org>
Subject: AW: Moving commits from one branch to another
Date: Wed, 23 Jan 2013 15:13:19 +0100 [thread overview]
Message-ID: <000b01cdf973$cc685fc0$65391f40$@de> (raw)
In-Reply-To: <20130123121203.GM7498@serenity.lan>
> > Is there any way to move/copy commits from one branch to another
> > without a common base-commit and without a forced push of master?
>
> Did you try "git rebase" with "--onto"? You probably want something
> like this:
>
> git rebase --onto svnbranch publishedToSvn master
I already tried this some days ago, but wasn't sure about the result. The
resulting history looks exactly what I expected, but all the commits are on
master after executing this commands and svnbranch only contains the
original two commits (svn-commit creating the root directory and the
cherry-picked commit from master)
Does the current branch matter if I call git-rebase with the
<branch>-argument?
next prev parent reply other threads:[~2013-01-23 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 12:04 Moving commits from one branch to another Stefan Schulze
2013-01-23 12:12 ` John Keeping
2013-01-23 14:13 ` Stefan Schulze [this message]
2013-01-23 14:49 ` John Keeping
2013-01-23 15:44 ` AW: " Schulze, Stefan
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='000b01cdf973$cc685fc0$65391f40$@de' \
--to=algroth@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).