From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: git-svnimport -- http/dav authentication notes
Date: Mon, 20 Feb 2006 20:24:17 +1300 [thread overview]
Message-ID: <46a038f90602192324v7193f154od4ff6952a68c799d@mail.gmail.com> (raw)
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.
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 ;-)
martin
next reply other threads:[~2006-02-20 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 7:24 Martin Langhoff [this message]
2006-02-20 19:22 ` git-svnimport -- http/dav authentication notes Eric Wong
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=46a038f90602192324v7193f154od4ff6952a68c799d@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--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