From: Sam Vilain <sam@vilain•net>
To: Jonathan del Strother <maillist@steelskies•com>
Cc: Eivind LM <eivliste@online•no>, git@vger•kernel.org
Subject: Re: Split a subversion repo into several git repos
Date: Fri, 12 Oct 2007 10:40:40 +1300 [thread overview]
Message-ID: <470E9858.5050904@vilain.net> (raw)
In-Reply-To: <27DDC599-C7A0-4660-B5C6-7DFCEB137C14@steelskies.com>
Jonathan del Strother wrote:
>> For example, I want to convert one subversion repository which
>> contains the folders:
>> trunk/projectA
>> trunk/projectB
>>
>> into two git repositories:
>> projectA.git
>> projectB.git
>
> I have a slightly different layout to you -
>
> projectA/trunk
> projectA/branches
> projectA/tags
> projectB/trunk
> projectB/branches
> projectB/tags
> etc
>
> - but I've been creating separate git repos from that with (for
> example) :
>
> git-svn init -t tags -b branches -T trunk http://svn.host.com/projectA
> git-svn fetch
>
>
> Or will git-svn not work with your sort of layout?
It does work. Use:
git-svn init -t projectA/tags -b projectA/branches \
-T trunk/projectA http://svn.host.com/
git fetch
Also you can expect the import results of each branch to be the same
regardless of whether you import all at once using a command like the
above, or import a single path without passing -t / -b / -T to git svn init.
If you have a lot of projects to mine from a single repository, use
svnsync or SVN::Mirror/svk and then import from the local repository
with --use-svm-props.
Sam.
next prev parent reply other threads:[~2007-10-11 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 12:51 Split a subversion repo into several git repos Eivind LM
2007-10-11 13:24 ` Patrick Doyle
2007-10-12 14:15 ` Eivind LM
2007-10-11 13:46 ` Jonathan del Strother
2007-10-11 14:02 ` Patrick Doyle
2007-10-11 14:50 ` Karl Hasselström
2007-10-11 21:40 ` Sam Vilain [this message]
2007-10-12 14:14 ` Eivind LM
2007-10-12 14:23 ` Jonathan del Strother
2007-10-12 14:47 ` Eivind LM
2007-10-12 20:27 ` Sam Vilain
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=470E9858.5050904@vilain.net \
--to=sam@vilain$(echo .)net \
--cc=eivliste@online$(echo .)no \
--cc=git@vger$(echo .)kernel.org \
--cc=maillist@steelskies$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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