Git-svn branch hoses dcommit when using an odd branch structure
- by Chuck Vose
I had a boss, past-tense, who decided to put svn branches in the same folder as trunk. Normally, this wouldn't affect me that much but since I'm using git-svn things are going so well. After I did a fetch it created a folder for each branch in my root folder so I have three folders, drupal, trunk, and client. The drupal folder is git's master branch, client and trunk are the svn branches.
Merging and committing works great, in fact everything git related is working superb. However dcommit is totally hosed, it's trying to commit a folder called client and one called trunk. I can't even imagine what havoc this would cause for svn later on.
So my question is, what have I done wrong in my .git/config and is there anything I can do to fix this or am I going to have to suffer and go back to using svn?
Please don't make me go back. I don't think I can take it anymore. Bastard boss knows how to leave a legacy.
[svn-remote "svn"]
url = https://svn.mydomain.com/svn/project_name
fetch = trunk:refs/remotes/trunk
branches = *:refs/remotes/*
tags = tags/*:refs/remotes/tags/*
Normally the branches line would look like this (when using --stdlayout):
branches = branches/*:refs/remotes/branches/*
ls output is thus:
$ ls
client/ docs/ drupal/ sql/ trunk/
