From: Michael J Gruber <git@drmicha.warpmail.net>
To: "\"Alejandro R. Sedeño\"" <asedeno@mit.edu>
Cc: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>,
James Y Knight <jknight@itasoftware.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] git-svn: Add a svn-remote.<name>.pushurl config key
Date: Wed, 06 Apr 2011 14:53:54 +0200 [thread overview]
Message-ID: <4D9C6262.2080408@drmicha.warpmail.net> (raw)
In-Reply-To: <4D9B7A9E.6040902@mit.edu>
"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
next prev parent reply other threads:[~2011-04-06 12:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 19:09 [PATCHv2 0/2] a couple of git-svn patches Alejandro R. Sedeño
2011-04-04 19:09 ` [PATCH 1/2] git-svn: Fix the commit-url config to be the base url, just like the url config Alejandro R. Sedeño
2011-04-04 21:52 ` Eric Wong
2011-04-04 22:16 ` James Y Knight
2011-04-04 22:54 ` Eric Wong
2011-04-05 15:11 ` "Alejandro R. Sedeño"
2011-04-05 20:15 ` [PATCH] git-svn: Add a svn-remote.<name>.pushurl config key Alejandro R. Sedeño
2011-04-05 20:25 ` "Alejandro R. Sedeño"
2011-04-05 21:09 ` Eric Wong
2011-04-06 12:53 ` Michael J Gruber [this message]
2011-04-06 13:04 ` "Alejandro R. Sedeño"
2011-04-06 13:12 ` Michael J Gruber
2011-04-06 15:05 ` Alejandro R. Sedeño
2011-04-06 15:22 ` Michael J Gruber
2011-04-06 15:34 ` "Alejandro R. Sedeño"
2011-04-06 15:38 ` Michael J Gruber
2011-04-08 14:57 ` Alejandro R. Sedeño
2011-04-08 20:13 ` Junio C Hamano
2011-04-08 20:25 ` Michael J Gruber
2011-04-08 20:54 ` Jeff King
[not found] ` <7v4o6830cc.fsf@alter.siamese.dyndns.org>
2011-04-08 21:32 ` Jeff King
2011-04-08 22:25 ` Junio C Hamano
2011-04-08 22:40 ` Jeff King
2011-04-08 22:43 ` Jeff King
2011-04-22 19:11 ` "Alejandro R. Sedeño"
2011-04-22 19:36 ` Jeff King
2011-04-22 19:40 ` "Alejandro R. Sedeño"
2011-04-09 22:47 ` Eric Wong
2011-04-06 12:44 ` Michael J Gruber
2011-04-06 12:56 ` "Alejandro R. Sedeño"
2011-04-04 19:09 ` [PATCH 2/2] git-svn: Cache results of running the executable "git config" Alejandro R. Sedeño
2011-04-04 21:53 ` Eric Wong
[not found] ` <7voc4l5hm5.fsf@alter.siamese.dyndns.org>
2011-04-05 8:15 ` Junio C Hamano
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=4D9C6262.2080408@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=asedeno@mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jknight@itasoftware.com \
--cc=normalperson@yhbt.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.