From: John Keeping <john@keeping.me.uk>
To: Stefan Schulze <algroth@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Moving commits from one branch to another
Date: Wed, 23 Jan 2013 14:49:41 +0000 [thread overview]
Message-ID: <20130123144941.GO7498@serenity.lan> (raw)
In-Reply-To: <000b01cdf973$cc685fc0$65391f40$@de>
On Wed, Jan 23, 2013 at 03:13:19PM +0100, Stefan Schulze wrote:
> > > 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)
Ah, I missed that you wanted to update svnbranch. I don't think there's
a single command that will do that, but this should work:
git rebase --onto svnbranch publishedToSvn master^0
git checkout -B svnbranch HEAD
This uses a detached head to avoid modifying the wrong branch and then
updates "svnbranch" to point at that after the rebase.
> Does the current branch matter if I call git-rebase with the
> <branch>-argument?
No it will checkout that branch first.
John
next prev parent reply other threads:[~2013-01-23 14:50 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 ` AW: " Stefan Schulze
2013-01-23 14:49 ` John Keeping [this message]
2013-01-23 15:44 ` 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=20130123144941.GO7498@serenity.lan \
--to=john@keeping.me.uk \
--cc=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).