From: Rogan Dawes <lists@dawes.za.net>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-svn and googlecode.com?
Date: Tue, 05 Jun 2007 10:11:25 +0200 [thread overview]
Message-ID: <46651AAD.4010705@dawes.za.net> (raw)
Hi,
Thanks to Martin, I got git svnimport working on the Spring Rich Client
Sourceforge repository. The published SVN checkout command line was:
svn co https://spring-rich-c.svn.sourceforge.net/svnroot/spring-rich-c \
spring-rich-c
This translated into a git svnimport invocation of:
git-svnimport -i -v -o origin -T trunk/spring-richclient -t tags \
-b branches \
https://spring-rich-c.svn.sourceforge.net/svnroot/spring-rich-c/
which works very well.
From this I assume that the usual translation from Sourceforge
published command lines works something like:
git svnimport -i -v -o origin -T trunk/<first path component> -t tags \
-b branches <URL>
Using a similar approach for a repo at code.google.com, I tried:
(Original) svn checkout http://webgoat.googlecode.com/svn/trunk/ webgoat
(Funny, the initial path component had a space in it?!)
0 $ git-svn clone -T "trunk/ webgoat"
https://webgoat.googlecode.com/svn/trunk/
Initialized empty Git repository in .git/
Using higher level of URL: https://webgoat.googlecode.com/svn/trunk =>
https://webgoat.googlecode.com/svn
W: Ignoring error from SVN, path probably does not exist: (175002): RA
layer request failed: REPORT request failed on '/svn/!svn/bc/100':
REPORT of '/svn/!svn/bc/100': 200 OK (https://webgoat.googlecode.com)
Path 'trunk/trunk/ webgoat' was probably deleted:
RA layer request failed: REPORT request failed on '/svn/!svn/bc/126':
REPORT of '/svn/!svn/bc/126': 200 OK (https://webgoat.googlecode.com)
Will attempt to follow revisions r101 .. r126 committed before the deletion
0 $
This didn't actually do anything other than creating the .git directory
structure, and creating one svn related file, even though it exited with
a zero status (the prompt above includes the exit status of the previous
command), and gave no diagnostics or error messages (other than "Using
higher level . . . ")
1 $ find .git
.git
.git/branches
.git/config
.git/description
.git/HEAD
.git/hooks
.git/hooks/applypatch-msg
.git/hooks/commit-msg
.git/hooks/post-commit
.git/hooks/post-receive
.git/hooks/post-update
.git/hooks/pre-applypatch
.git/hooks/pre-commit
.git/hooks/pre-rebase
.git/hooks/update
.git/info
.git/info/exclude
.git/objects
.git/objects/info
.git/objects/pack
.git/refs
.git/refs/heads
.git/refs/tags
.git/remotes
.git/svn
.git/svn/.metadata
.git/svn/trunk
.git/svn/trunk/.rev_db.4033779f-a91e-0410-96ef-6bf7bf53c507
However, the following command line does seem to work:
git-svn clone -T "trunk/ webgoat" https://webgoat.googlecode.com/svn/
Note that I manually removed the "trunk" component from the URL. This
suggests that there is something missing in the automatic "Using higher
level" detection code.
Hope this helps someone diagnose this bug, as well as use git for
accessing GoogleCode projects in the future.
Rogan
next reply other threads:[~2007-06-05 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 8:11 Rogan Dawes [this message]
2007-06-05 9:05 ` git-svn and googlecode.com? Andy Parkins
2007-06-05 10:11 ` Rogan Dawes
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=46651AAD.4010705@dawes.za.net \
--to=lists@dawes.za.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;
as well as URLs for NNTP newsgroup(s).