From: Victor Engmark <victor.engmark@terreactive.ch>
To: git@vger.kernel.org
Subject: git svn dcommit sends to wrong branch
Date: Tue, 10 Jan 2012 17:18:43 +0100 [thread overview]
Message-ID: <20120110161843.GC8196@victor> (raw)
Commands:
git svn clone -s -r 1:HEAD http://svn/repo
cd repo
git commit [thrice, in master only]
git rebase --interactive HEAD~20 [i.e., started rebase in commits before
the clone]
[Merged two commits I had made *after* the clone]
git commit ...
git dcommit
This created commits on
<http://svn/repo/branches/branch_name>! Why? Is it because HEAD~20's
git-svn-id <http://svn/repo/branches/branch_name@22481> is on that
branch?
And more importantly, how do I "replay" my commits on trunk?
--
terreActive AG
Kasinostrasse 30
CH-5001 Aarau
Tel: +41 62 834 00 55
Fax: +41 62 823 93 56
www.terreactive.ch
Wir sichern Ihren Erfolg - seit 15 Jahren
next reply other threads:[~2012-01-10 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 16:18 Victor Engmark [this message]
2012-01-10 19:43 ` git svn dcommit sends to wrong branch Thomas Rast
2012-01-11 14:05 ` Victor Engmark
2012-01-11 15:31 ` Thomas Rast
2012-01-26 15:27 ` badgerhardy
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=20120110161843.GC8196@victor \
--to=victor.engmark@terreactive.ch \
--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).