git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniele Segato <daniele.bilug@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-svn-Cloning repository with complex nesting
Date: Mon, 31 Aug 2009 09:41:28 +0200	[thread overview]
Message-ID: <9accb4400908310041j45d2d1bar9e61348e355892b9@mail.gmail.com> (raw)

On Thu, Aug 27, 2009 at 10:32 AM, Daniele Segato<daniele.bilug@gmail.com> wrote:
> Hi, this is my first message in the list: this may be a newbie
> question and my English may not be very good.

to prove my sentence:
the subject should have been "git-svn-Cloning repository with
_complex_ nesting" :-)

I received help on IRC (#git) and managed to setup the svn-remote in
an acceptable way

> I've an SVN repository structured like this:
>
> http://<url>/path/to/repo
>    |
>  HEAD
>    |----- root
>    |
>  BRANCHES
>    |----- V1.0
>    |         |----- root
>    |
>    |----- V1.1
>    |         |----- root
>    |
>    |----- V1.2
>    |         |----- root
>    |
>    |----- DEV
>    |         |----- FEATURE1
>    |         |            |----- root
>    |         |
>    |         |----- FEATURE2
>    |         |            |----- root
>    |         |
>    |         |----- FEATURE3
>    |                      |----- root
>    |
>    |----- BUILDS
>              |----- BUILD1
>              |            |----- root
>              |
>              |----- BUILD2
>              |            |----- root
>              |
>              |----- BUILD3
>                           |----- root


this is my setting:

git init
git svn init svn://svn.mydomain.com/path/to/repo -T HEAD -b BRANCHES -t TAGS

vim .git/config # edited the svn-remote config as follow:
[svn-remote "svn"]
	url = svn://svn.mydomain.com
	fetch = path/to/repo/HEAD/root:refs/remotes/svn/trunk
	branches = path/to/repo/BRANCHES/*/root:refs/remotes/svn/*
	tags = path/to/repo/TAGS/*/root:refs/remotes/svn/tags/*

git svn fetch

it seems to work as expected: only those branches that has a "root"
folder got downloaded and fetched.

I still couldn't retrieve the DEV/FEATUREx branches in that way.
On IRC they told me I can add another line for branches:

branches = path/to/repo/BRANCHES/*/*/root:refs/remotes/svnbis/*

but I haven't been successful on this. They told me that I can add
multiple branches lines only on newer versions of git.
Probably that's the reason for that.
I have git version 1.5.6.5.

It is not a big deal: I can live without those branches even if I'll
like to have them too.

I have another problem now on that SVN repo but I'll open another
topic about that because it is not related.

Regards,
Daniele

                 reply	other threads:[~2009-08-31  7:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9accb4400908310041j45d2d1bar9e61348e355892b9@mail.gmail.com \
    --to=daniele.bilug@gmail.com \
    --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).