From: Nicolas Pitre <nico@cam.org>
Date: Wed, 30 Nov 2005 03:54:21 GMT
Subject: Re: [PATCH] SVN import: Use one log call
Message-ID: <Pine.LNX.4.64.0511292247591.3122@localhost.localdomain>
In-Reply-To: <7vhd9vdx1o.fsf@assigned-by-dhcp.cox.net>

On Tue, 29 Nov 2005, Junio C Hamano wrote:

> BTW, I've never successfully managed to run svnimport from my
> private svn repository.

Same here, with the following public repo: svn://mielke.cc/main/brltty

> $ git svnimport -v -i -t photocat http://127.0.0.1/svn/private main/sources
> 1: Unrecognized path: /main/sources
> 1: Unrecognized path: /main/in-place
> 1: Unrecognized path: /main
> ...
> 1500: Unrecognized path: /main/sources/photocat/db/catalog.sql
> 1501: Unrecognized path: /main/sources/photocat/data/035-maribon-making.yaml
> DONE; creating master branch
> cp: cannot stat `/var/tmp/try0/.git/refs/heads/origin': No such file or directory
> fatal: master: not a valid SHA1
> $ 

And I only get similar results.

> If your answer is "your repository layout is too weird and
> nonstandard, you are screwed", that is perfectly fine.  I do not
> want you to bend over backwards to butcher the import script to
> support it, if it is too nonstandard.

Thing is the above repository is not _that_ weird.  And with the real 
svn it produces a proper source tree of course, without any special 
options.  So I would think git-svnimport should be able to do the same.  
No?


Nicolas