From: "Patrick Doyle" <wpdster@gmail.com>
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: Thu, 11 Oct 2007 10:02:21 -0400 [thread overview]
Message-ID: <e2a1d0aa0710110702o359d6cd9yaa213be6a43924e4@mail.gmail.com> (raw)
In-Reply-To: <27DDC599-C7A0-4660-B5C6-7DFCEB137C14@steelskies.com>
On 10/11/07, Jonathan del Strother <maillist@steelskies.com> wrote:
> 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
>
Just be aware that, if you follow this approach, the commit logs
created by git-svn will be rewritten (relative to the original SVN
logs) with the SVN repository revision and ID information. I believe
you can disable this behavior by passing the --no-metadata option to
"git-svn init", but I haven't tried this yet.
I also believe that this approach will leave your git repository in
such as state as to recognize that there is a remote repository from
which this repository was fetched. I have no idea what implications
and long term repercussions (if any) this has. It just dawned on me
as I was rereading the git-svn man page to look for the --no-metdata
option and read that it will "Set the noMetadata option in the
[svn-remote] config". Most of that is still Greek to me.
--wpd
next prev parent reply other threads:[~2007-10-11 14:02 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 [this message]
2007-10-11 14:50 ` Karl Hasselström
2007-10-11 21:40 ` Sam Vilain
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=e2a1d0aa0710110702o359d6cd9yaa213be6a43924e4@mail.gmail.com \
--to=wpdster@gmail.com \
--cc=eivliste@online.no \
--cc=git@vger.kernel.org \
--cc=maillist@steelskies.com \
/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).