git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Sebastian Pipping <webmaster@hartwork.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	git@vger.kernel.org, "Nicolas Sebrecht" <nicolas.s.dev@gmx.fr>
Subject: [BUG?] Re: fail to svn clone debian's kernel repository
Date: Tue, 2 Mar 2010 20:54:54 +0100	[thread overview]
Message-ID: <20100302195454.GB12942@vidovic> (raw)
In-Reply-To: <4B8B21A8.6000603@hartwork.org>

The 01/03/10, Sebastian Pipping wrote:
> On 06/10/09 18:05, Uwe Kleine-König wrote:
> > Hello,
> > 
> > using git v1.6.3.1 from Debian I fail to successfully run
> > 
> > 	git svn clone svn://svn.debian.org/kernel/dists/trunk/linux-2.6
> > 
> > It runs for some time and then ends in:
> > 
> > 	...
> > 	r4695 = f552d98386b301cbeaa3b5a20f9e9d5d3c9c4886 (git-svn)
> > 		M	debian/arch/alpha/defines
> > 	r4696 = 18c0a37de057d24955b66e8f49db0791f6018288 (git-svn)

<...>

> > 	Invalid filesystem path syntax: Cannot replace a directory from within at /usr/lib/git-core/git-svn line 4388
> 
> I have run into a similar problem, both with Git 1.7.0 as well as with
> Git via Git.
> 
> Has anybody been able to work around this?
> Is anybody working on a fix?

I've stopped cloning at r10252 with current next version. I didn't
notice any problem.

Does the tests pass for you ?

  $ cd t
  $ make

-- 
Nicolas Sebrecht

  reply	other threads:[~2010-03-02 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 16:05 [BUG?] fail to svn clone debian's kernel repository Uwe Kleine-König
2009-06-10 18:42 ` Uwe Kleine-König
2010-03-01  2:08 ` Sebastian Pipping
2010-03-02 19:54   ` Nicolas Sebrecht [this message]
2010-03-03  1:20     ` [BUG?] " Sebastian Pipping
2010-03-03 14:33       ` Thomas Rast
2010-03-04  2:03         ` Sebastian Pipping

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=20100302195454.GB12942@vidovic \
    --to=nicolas.s.dev@gmx.fr \
    --cc=git@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=webmaster@hartwork.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;
as well as URLs for NNTP newsgroup(s).