git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rogan Dawes <lists@dawes.za.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>, normalperson@yhbt.net
Subject: Re: svnimport problems (abysmal performance and crash) on Cygwin
Date: Tue, 13 Mar 2007 21:23:15 +0100	[thread overview]
Message-ID: <45F70833.5080800@dawes.za.net> (raw)
In-Reply-To: <46a038f90703131303r6a50c077n7144ddb0045062db@mail.gmail.com>

Martin Langhoff wrote:
> On 3/14/07, Rogan Dawes <lists@dawes.za.net> wrote:
>> Any suggestions for how *I* can figure it out?
> 
> Well -- all my experience with SVN has been when using it with
> svnimport ;-) and trying again and again.
> 
>  From looking at this url
> http://spring-rich-c.svn.sourceforge.net/svnroot/spring-rich-c/ I
> suspect that you might want to invoke it like
> 
> git-svnimport -T trunk -t tags -b branches
> http://spring-rich-c.svn.sourceforge.net/svnroot/spring-rich-c/
> 
> (note the shorter url).
> 
> If that works but leaves the main project in a subdirectory, but the
> trees in branches and tags without the subdirectory, you might want to
> try:
> 
> git-svnimport -T trunk/spring-richclient -t tags -b branches
> http://spring-rich-c.svn.sourceforge.net/svnroot/spring-rich-c/
> 
> It might take a couple of tries. NOTE: you should check not only the
> main dev track but also the branches and tags for sanity.
> 
> cheers
> 
> 
> m

That seems to be working now, with the second commandline that you 
suggested. I'll still verify the tags, but I think that the branches are 
less likely to be a problem, since the project hasn't actually made any, 
as far as I am aware (at least, none that I am interested in).

Thanks for your help!

Rogan

      reply	other threads:[~2007-03-13 20:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12  6:39 svnimport problems (abysmal performance and crash) on Cygwin Rogan Dawes
2007-03-12  7:24 ` Rogan Dawes
2007-03-12 10:39   ` Martin Langhoff
2007-03-12 17:44     ` Rogan Dawes
2007-03-13 19:10       ` Rogan Dawes
2007-03-13 19:50         ` Martin Langhoff
2007-03-13 19:51           ` Rogan Dawes
2007-03-13 20:03             ` Martin Langhoff
2007-03-13 20:23               ` Rogan Dawes [this message]

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=45F70833.5080800@dawes.za.net \
    --to=lists@dawes.za.net \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    --cc=normalperson@yhbt.net \
    /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).