From: Daniel Barkalow <barkalow@iabervon.org>
To: Boyd Lynn Gerber <gerberb@zenez.com>
Cc: Miklos Vajna <vmiklos@frugalware.org>, Git List <git@vger.kernel.org>
Subject: Re: git-svn-import or CVS import from local HD rather than remote.
Date: Thu, 12 Jun 2008 16:56:13 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.1.00.0806121652220.19665@iabervon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0806121348340.18454@xenau.zenez.com>
On Thu, 12 Jun 2008, Boyd Lynn Gerber wrote:
> On Thu, 12 Jun 2008, Daniel Barkalow wrote:
> > On Thu, 12 Jun 2008, Boyd Lynn Gerber wrote:
> > > On Thu, 12 Jun 2008, Miklos Vajna wrote:
> > > > On Thu, Jun 12, 2008 at 12:36:43PM -0600, Boyd Lynn Gerber
> > > > <gerberb@zenez.com> wrote:
> > > > > git-svnimport -C /working/git/project /master/svn/pub-svn/category/project
> > > >
> > > > From RelNotes-1.5.4.txt:
> > > >
> > > > * "git svnimport" was removed in favor of "git svn". It is still there
> > > > in the source tree (contrib/examples) but unsupported.
> > > >
> > > > Try using git-svn.
> > >
> > > Thanks, I was not sure which I should use, I had tried both with similar
> > > results. Here is what I used with git-svn
> > >
> > > > git-svn clone /working/svn/networking/wireshark .
> > > Initialized empty Git repository in .git/
> > > Bad URL passed to RA layer: Unrecognized URL scheme for
> > > '/working/svn/networking/wireshark' at /usr/bin/git-svn line 934
> >
> > Maybe file:///working/svn/networking/wireshark?
>
> This is really frustrating.
>
> I have tried every combination of file://localhost/ file:///
>
> This is what I get
>
> git-svn clone file:///working/svn/network/wireshark/ -T trunk -b branches
> -t tags wireshark
> Initialized empty Git repository in .git/
> Couldn't open a repository: Unable to open an ra_local session to URL:
> Unable to open repository 'file:///working/svn/network/wireshark' at
> /usr/bin/git-svn line 1048
>
> > ls -la /working/svn/network/wireshark/
> total 16
> drwxr-xr-x 8 gerberb zenez 208 2008-06-10 12:44 .
> drwxr-xr-x 9 gerberb zenez 240 2008-06-12 13:00 ..
> drwxr-xr-x 6 gerberb zenez 240 2008-06-12 12:14 .svn
> drwxr-xr-x 6 gerberb zenez 152 2008-06-10 12:43 historic
> drwxr-xr-x 5 gerberb zenez 152 2008-06-10 12:46 prereleases
> drwxr-xr-x 86 gerberb zenez 2728 2008-06-10 12:37 releases
> drwxr-xr-x 26 gerberb zenez 7016 2008-06-10 12:39 trunk
> drwxr-xr-x 25 gerberb zenez 7136 2008-06-10 11:45 trunk-1.0
That looks like a SVN working copy, not an SVN repository. Maybe you want
file:///master/svn/...?
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2008-06-12 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 18:36 git-svn-import or CVS import from local HD rather than remote Boyd Lynn Gerber
2008-06-12 18:55 ` Miklos Vajna
2008-06-12 19:20 ` Boyd Lynn Gerber
2008-06-12 19:23 ` Miklos Vajna
2008-06-12 19:24 ` Daniel Barkalow
2008-06-12 19:57 ` Boyd Lynn Gerber
2008-06-12 20:41 ` Miklos Vajna
2008-06-12 20:46 ` Boyd Lynn Gerber
2008-06-12 20:56 ` Daniel Barkalow [this message]
2008-06-12 21:03 ` Boyd Lynn Gerber
2008-06-12 22:11 ` Daniel Barkalow
2008-06-12 22:20 ` Boyd Lynn Gerber
2008-06-13 4:00 ` Asheesh Laroia
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=alpine.LNX.1.00.0806121652220.19665@iabervon.org \
--to=barkalow@iabervon.org \
--cc=gerberb@zenez.com \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.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