On 10/11/07, Jonathan del Strother <maillist@xxxxxxxxxxxxxx> 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
