Subject: Re: [PATCH] git-svn: Add a svn-remote.<name>.pushurl config key

From: Michael J Gruber <[email-masked]>
Date: Wed, 06 Apr 2011 14:53:54 +0200

"Alejandro R. Sedeño" venit, vidit, dixit 05.04.2011 22:25:
> On 04/05/2011 04:15 PM, Alejandro R. Sedeño wrote:
>> @@ -730,7 +736,11 @@ sub cmd_branch {
>>  		$url = eval { command_oneline('config', '--get',
>>  			"svn-remote.$gs->{repo_id}.commiturl") };
>>  		if (!$url) {
>> -			$url = $remote->{url};
>> +			$url = eval { command_oneline('config', '--get',
>> +				      "svn-remote.$gs->{repo_id}.pushurl") };
>> +			if (!$url) {
>> +				$url = $remote->{url};
>> +			}
>>  		}
>>  	}
>>  	my $dst = join '/', $url, $lft, $branch_name, ($rgt || ());
> 
> Actually, I was just finishing running this through its paces with
> different values for url and pushurl, and branching has issues:
> 
> Trying to use an unsupported feature: Source and dest appear not to be in
> the same repository (src: 'http://asedeno/svn/trunk'; dst:
> 'file:///tmp/svn/repo/branches/nb1') at /tmp/git/libexec/git-core/git-svn
> line 770
> 
> So I'm continuing to look into that. Perhaps it makes sense to use pushurl
> for both src and dst when branching?

For branching, yes. This is just the following in disguise:

http://permalink.gmane.org/gmane.comp.version-control.git/135577

"svn cp" between 2 URLs simply requires they're within the same repo.

Michael