On Sat, May 26, 2007 at 10:10:46AM -0500, Art Haas wrote: > On Sat, May 26, 2007 at 03:06:43PM +0200, Frank Lichtenheld wrote: > > On Sat, May 26, 2007 at 07:55:53AM -0500, Art Haas wrote: > > > I'm happy to dive into the perl code in svnimport and make changes to > > > help debug this problem, if there is actually a problem and not user > > > error on my part. Any help from 'svnimport' experts will be greatly > > > appreciated. The public repo listed above has the same contents as my > > > local repo, so feel free to poke around it to see how things are > > > structured. > > > > You might want to try git-svn instead. It should support everything you > > can do with git-svnimport and much more. Plus it is actively maintained > > which I wouldn't say about git-svnimport. > > Hi. > > The git-svn docs say that it serves as a bi-directionaly gateway It can be happily used for one-time imports, too. You might want to use some options like the authors file and perhaps --no-metadata. Can't say much about the rest of your plans since I'm no git-svn expert. I have only ever used it for one-time imports so far. > between git and svn, but that the main repo is a Subversion repository. > My goal with the PythonCAD repo is to convert it so that the main > repository is in git, and then I'm going to try to use git-svn to > push my changes into the now-secondary Subversion repo. This way, I can > make a distributed git repo available to developers wanting to > contribute to PythonCAD, plus keep the developers currently using > Subversion from having to make any changes if they either don't want to > or are unable to (i.e. windows developers/users). > > Is git-svnimport maintenence on the wane? Search the archive of the last month for posts on git-svnimport... IIRC there was one typo fix and one thread about a problem with it that ended in the question wether it should be removed. Gruesse, -- Frank Lichtenheld <frank@xxxxxxxxxxxxxx> www: http://www.djpig.de/ - 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
