All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rutger Nijlunsing <rutger@nospam.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>, git@vger.kernel.org
Subject: Re: git-svnimport on OSX?
Date: Tue, 11 Apr 2006 01:00:16 +0200	[thread overview]
Message-ID: <20060410230016.GA28078@nospam.com> (raw)
In-Reply-To: <46a038f90604031911y415dd795nc1c8814f80a02ad7@mail.gmail.com>

On Tue, Apr 04, 2006 at 02:11:02PM +1200, Martin Langhoff wrote:
> On 03 Apr 2006 18:04:07 -0700, Randal L. Schwartz <merlyn@stonehenge.com> wrote:
> >
> > Working for anyone?  Not working for me, and just wondered if it was me or a
> > known thing.  Maybe I'm just holding my mouth wrong, and yes, I have SVN::Core
> > installed.  If anyone wants details, I can provide.
> 
> I think I tried and gave up on it a month or two ago, but can't
> remember the details. Fink's SVN::Core is too old, and having all the
> SVN toolchain is a pain. What is the problem?
> 
> BTW, getting git-svnimport to work normally takes me quite a few tries
> with different options, so OSX may be perfectly innocent this time...

Could you try http://www.wingding.demon.nl/git-svnconvert.rb on
MacOSX? This one doesn't need SVN::Core, and I'm curious on what to
change for MacOSX.

By default it imports all branches it can find (see in file itself):

...
$branch_dirs = %q{
  /branches/*
  /trunk
}
...

If your layout is different (for example, like
http://svn.perl.org/perl6 where every subdir is a collection of
branches itself), use something like:

...
$branch_dirs = %q{
  */branches/*
  */trunk
}
...



-- 
Rutger Nijlunsing ---------------------------------- eludias ed dse.nl
never attribute to a conspiracy which can be explained by incompetence
----------------------------------------------------------------------

      parent reply	other threads:[~2006-04-10 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04  1:04 git-svnimport on OSX? Randal L. Schwartz
2006-04-04  2:11 ` Martin Langhoff
2006-04-10 14:43   ` Randal L. Schwartz
2006-04-10 23:00   ` Rutger Nijlunsing [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=20060410230016.GA28078@nospam.com \
    --to=rutger@nospam.com \
    --cc=git@vger.kernel.org \
    --cc=git@wingding.demon.nl \
    --cc=martin.langhoff@gmail.com \
    --cc=merlyn@stonehenge.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.