From: Frank Lichtenheld <frank@lichtenheld.de>
To: Art Haas <ahaas@airmail.net>
Cc: git@vger.kernel.org
Subject: Re: Problems importing SVN repo via git-svnimport
Date: Sat, 26 May 2007 17:34:43 +0200 [thread overview]
Message-ID: <20070526153443.GC2674@planck.djpig.de> (raw)
In-Reply-To: <20070526151046.GA2239@artsapartment.org>
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@lichtenheld.de>
www: http://www.djpig.de/
prev parent reply other threads:[~2007-05-26 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 12:55 Problems importing SVN repo via git-svnimport Art Haas
2007-05-26 13:06 ` Frank Lichtenheld
2007-05-26 15:10 ` Art Haas
2007-05-26 15:34 ` Frank Lichtenheld [this message]
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=20070526153443.GC2674@planck.djpig.de \
--to=frank@lichtenheld.de \
--cc=ahaas@airmail.net \
--cc=git@vger.kernel.org \
/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