Re: git-svn and googlecode.com?
- From
- Andy Parkins <andyparkins@gmail.com>
- Date
- Jun 5, 2007, 09:05 UTC
- Message-ID
- <200706051005.46603.andyparkins@gmail.com>
- In-Reply-To
- <46651AAD.4010705@dawes.za.net>
On Tuesday 2007 June 05, Rogan Dawes wrote:
> (Original) svn checkout http://webgoat.googlecode.com/svn/trunk/ webgoat > > (Funny, the initial path component had a space in it?!)
I suspect that that is not the case. The form of svn checkout is:
svn checkout <url> <directory>
So your command is saying check out http://webgoat.googlecode.com/svn/trunk/ to the local directory "webgoat". That is to say - it doesn't have a space in it and in fact is nothing to do with the URL at all.
Show 9 quoted lines
> 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:
... which explains this error because there is no path "trunk/ webgoat".
> However, the following command line does seem to work: > > git-svn clone -T "trunk/ webgoat" https://webgoat.googlecode.com/svn/
Oh dear; I'm surprised it worked as well as it did. I just ran this command, which seemed to work well:
$ git-svn clone -T trunk http://webgoat.googlecode.com/svn/ webgoat-local
This clones webgoat.googlecode.com/svn to the local directory webgoat-local; you can change "webgoat-local" to anything you want, it's just naming the directory on your own computer.
If you're the maintainer then perhaps you will want to change "http" to "https" as well.
> 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.
I think there is no bug; it's simply a misunderstanding. git-svn working wonderfully for me.
Andy
-- Dr Andy Parkins, M Eng (hons), MIET andyparkins@gmail.com