From: "Craig Tataryn" <craiger@tataryn.net>
To: git@vger.kernel.org
Subject: Help with merge and git-svn
Date: Fri, 26 Sep 2008 11:36:48 -0500 [thread overview]
Message-ID: <8384c2b90809260936m21c14e0dve5b08b021da4a342@mail.gmail.com> (raw)
Hi, first time poster to kernel.org mailing lists, so if I commit a
taboo, please be kind to me :)
I have the following scenario:
[remote deveoper]<===>[shared git repo]<===>[me]<===>[client's svn repo]
So my remote developer and I push and pull to/from the shared git
repo, and then I sync changes to and from the client's svn repo using
git-svn.
My problem is, when I am ready to merge changes from my local master
branch to trunk-local, if I do a "git merge master" and then try to
issue any git-svn commands I get the following errors:
======================
$ git merge master
Updating d88106e..77b86ae
Fast forward
community/pom.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
$ git svn dcommit
Can't call method "full_url" on an undefined value at
/usr/local/git/libexec/git-core/git-svn line 425.
$ git svn rebase
Unable to determine upstream SVN information from working tree history
======================
The only way I've seem to be able to remedy this is if I add the
"subtree" merge strategy to the merge command:
git merge -s subtree master
Then git-svn doesn't get confused about it's repo, but when you look
at the repo using gitk, you see something like:
[trunk-local]--[remotes/trunk] Merge branch 'master' into trunk-local
| \
| \
| [master]--[remotes/origin/master] "Some commit message from the
last master commit"
| |
| |
| /
/
When I use the normal merge strategy then gitk shows all branches at
the same level, but git-svn is of course b0rked.
So I guess my question is, am I stuck using "-s subtree", is this the
right course of action?? Or can I get this to work with the default
strategy? Is this symptomatic of a messed up or disjoint history
(i.e. early on I did some --squash merges).
I have full control over the shared repo and I don't mind blowing it
away and rebuilding it based on what's in SVN if that's what it takes.
Thanks!
Craig.
--
Craig Tataryn
site: http://www.basementcoders.com/
podcast:http://feeds.feedburner.com/TheBasementCoders
irc: ThaDon on freenode #basementcoders, ##wicket, #papernapkin
im: craiger316@hotmail.com, skype: craig.tataryn
next reply other threads:[~2008-09-26 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 16:36 Craig Tataryn [this message]
2008-09-26 17:23 ` Help with merge and git-svn Björn Steinbrink
2008-09-26 18:02 ` Craig Tataryn
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=8384c2b90809260936m21c14e0dve5b08b021da4a342@mail.gmail.com \
--to=craiger@tataryn.net \
--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).