From: Eric Wong <normalperson@yhbt.net>
Date: Mon, 20 Feb 2006 19:22:25 GMT
Subject: Re: git-svnimport -- http/dav authentication notes
Message-ID: <20060220192225.GB18085@hand.yhbt.net>
In-Reply-To: <46a038f90602192324v7193f154od4ff6952a68c799d@mail.gmail.com>

Martin Langhoff <martin.langhoff@gmail.com> wrote:
> After a lot of trial and error against a server I don't control (so I
> can't log things on) I've managed to use svn-import on it and it
> mostly seems to work. Kind of. It's slowly grinding through the
> commits.
> 
> To make it short, I seem to be doing well with:
> 
>    git-svnimport -t tags -T trunk -b branches -o svntrunk -v
>          'http://martin%40catalyst.net.nz:password@nameless.server.org/svn/someproject'
> 
> The repo has LDAP authentication, and the username is my email
> address, so I guessed that url-encoding would work, and it did.

Logging in with the svn command-line client (svn ls <url>) be enough to
cache auth information for the SVN library (and therefore svnimport)?
Unless you've disabled it in your config, of course...

> svnimport is a bit of a mistery actually. I often know if it's really
> doing the import or the files are going to be there but empty. SVN is
> so flexible in its "everything is a directory" way of thinking that if
> I mess up -t or -b I get the commits alright... but no files.
> 
> Strange world, svn ;-)

Hear, hear.  I always had to reread the manpage or look here for
examples on how to use it.  And then echo !! > .git/info/svnimport-cmd
after I was done using it so I wouldn't have to remember which command
switches I used.

Then I decided to write git-svn :>

-- 
Eric Wong