conversion from svn with renames

conversion from svn with renames

[Ricardo SIGNES]

I'd like to convert svn.codesimply.com/projects' contents to git.

Right now, the content is like this:

  /projects/$PROJECTNAME/{trunk,tags,branches}

git-svnimport does well if I specify projects/$PROJECTNAME/trunk as the trunk
directory and that/tags as the tags directory.  (I am not interested in
bothering with branches.)  The problem is this:

For many of the projects, $PROJECTNAME was once "foo" and is now "bar."
git-svnimport only imports the history from the current name.

I tried to import foo, then bar, into one git repostiory, but the histories
didn't seem to get connected.  Sam V. suggested git-filter-branch, but I didn't
quite see how to make it do what I wanted.

I would greatly appreciate any advice or help on this conversion.

-- 
rjbs

Re: conversion from svn with renames

[Väinö Järvelä]

Hi,

I tried importing an SVN project with svn-import, and the project had  
been renamed once. It seems that git-svn is more mature tool for this,  
even if svn-import seems to be the one to use. If I remember  
correctly, there was even talk about this very same case in the  
mailing list archives.

To make a complete conversion from SVN repository to GIT repositories,  
just use --no-metadata option to remove all the metadata git-svn  
normally appends to the commit messages. There will also be some cruft  
in the .git/config file, I removed those, and have had an working  
import with renames from SVN.

--
Väinö

On Jul 29, 2007, at 15:23, Ricardo SIGNES wrote:

>
> I'd like to convert svn.codesimply.com/projects' contents to git.
>
> Right now, the content is like this:
>
> /projects/$PROJECTNAME/{trunk,tags,branches}
>
> git-svnimport does well if I specify projects/$PROJECTNAME/trunk as  
> the trunk
> directory and that/tags as the tags directory.  (I am not interested  
> in
> bothering with branches.)  The problem is this:
>
> For many of the projects, $PROJECTNAME was once "foo" and is now  
> "bar."
> git-svnimport only imports the history from the current name.
>
> I tried to import foo, then bar, into one git repostiory, but the  
> histories
> didn't seem to get connected.  Sam V. suggested git-filter-branch,  
> but I didn't
> quite see how to make it do what I wanted.
>
> I would greatly appreciate any advice or help on this conversion.
>
> -- 
> rjbs
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: conversion from svn with renames

[Väinö Järvelä]

Eh, sorry for replying to a old post, I had accidentally had my mail  
sorted in reverse. I hope the post was still useful.

--
Väinö

On Nov 16, 2007, at 05:16, Väinö Järvelä wrote:

> Hi,
>
> I tried importing an SVN project with svn-import, and the project  
> had been renamed once. It seems that git-svn is more mature tool for  
> this, even if svn-import seems to be the one to use. If I remember  
> correctly, there was even talk about this very same case in the  
> mailing list archives.
>
> To make a complete conversion from SVN repository to GIT  
> repositories, just use --no-metadata option to remove all the  
> metadata git-svn normally appends to the commit messages. There will  
> also be some cruft in the .git/config file, I removed those, and  
> have had an working import with renames from SVN.
>
> --
> Väinö
>
> On Jul 29, 2007, at 15:23, Ricardo SIGNES wrote:
>
>>
>> I'd like to convert svn.codesimply.com/projects' contents to git.
>>
>> Right now, the content is like this:
>>
>> /projects/$PROJECTNAME/{trunk,tags,branches}
>>
>> git-svnimport does well if I specify projects/$PROJECTNAME/trunk as  
>> the trunk
>> directory and that/tags as the tags directory.  (I am not  
>> interested in
>> bothering with branches.)  The problem is this:
>>
>> For many of the projects, $PROJECTNAME was once "foo" and is now  
>> "bar."
>> git-svnimport only imports the history from the current name.
>>
>> I tried to import foo, then bar, into one git repostiory, but the  
>> histories
>> didn't seem to get connected.  Sam V. suggested git-filter-branch,  
>> but I didn't
>> quite see how to make it do what I wanted.
>>
>> I would greatly appreciate any advice or help on this conversion.
>>
>> -- 
>> rjbs
>> -
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html