From: "Jon Lim" <snowblink@gmail.com>
To: "Eric Wong" <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git svn clone -s was not prefixing 'branches/'
Date: Sat, 17 Jan 2009 11:39:28 +0000 [thread overview]
Message-ID: <751e526a0901170339m6471ac84tdb032a090d19d7c6@mail.gmail.com> (raw)
In-Reply-To: <20090117105427.GA15801@dcvr.yhbt.net>
Hi,
Maybe this patch doesn't fix the problem I was having. I will attempt
to describe it better here.
I understand that a standard subversion setup is as follows:
trunk
branches
tags
With the -s option, svn clone should expect this.
Using the example subversion repository:
trunk
branches/RB_1.0
branches/RB_2.0
tags/REL_1.0
tags/REL_2.0
Currently, using the -s option you get:
trunk
RB_1.0
RB_2.0
tags/REL_1.0
tags/REL_2.0
I think it makes sense to have:
trunk
branches/RB_1.0
branches/RB_2.0
tags/REL_1.0
tags/REL_2.0
Regards,
Jon
On Sat, Jan 17, 2009 at 10:54, Eric Wong <normalperson@yhbt.net> wrote:
> Jonathan Lim <snowblink@gmail.com> wrote:
>> All branches in the subversion repository would appear at the same
>> level as trunk. The should now appear with a 'branches/' prefix.
>>
>> Signed-off-by: Jonathan Lim <snowblink@gmail.com>
>
> This is too ugly for the common existing cases. For the rare case where
> this could lead to a namespace conflict[1], it's possible to work around
> it by editing .git/config.
>
> I would accept a --tags-prefix= and --branches-prefix= patch to make
> this possible w/o having to edit .git/config, but I don't want the
> default prefixes changed.
>
> Thanks,
>
> [1] - "/branches/trunk" vs "/trunk", which I've yet to see evidence of...
>
>> ---
>> git-svn.perl | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/git-svn.perl b/git-svn.perl
>> index ad01e18..17d65cb 100755
>> --- a/git-svn.perl
>> +++ b/git-svn.perl
>> @@ -789,7 +789,7 @@ sub cmd_multi_init {
>> }
>> return unless defined $_branches || defined $_tags;
>> my $ra = $url ? Git::SVN::Ra->new($url) : undef;
>> - complete_url_ls_init($ra, $_branches, '--branches/-b', $_prefix);
>> + complete_url_ls_init($ra, $_branches, '--branches/-b', $_prefix . 'branches/');
>> complete_url_ls_init($ra, $_tags, '--tags/-t', $_prefix . 'tags/');
>> }
>
--
http://snowblink.co.uk/
next prev parent reply other threads:[~2009-01-17 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1232050647-2870-1-git-send-email-snowblink@gmail.com>
2009-01-17 10:54 ` [PATCH] git svn clone -s was not prefixing 'branches/' Eric Wong
2009-01-17 11:39 ` Jon Lim [this message]
2009-01-17 12:07 ` Björn Steinbrink
2009-01-18 1:24 ` Eric Wong
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=751e526a0901170339m6471ac84tdb032a090d19d7c6@mail.gmail.com \
--to=snowblink@gmail.com \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox