From: Dennis Schridde <devurandom@gmx.net>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: git svn fetch segfaults
Date: Wed, 9 Jan 2008 13:53:41 +0100 [thread overview]
Message-ID: <200801091353.44630.devurandom@gmx.net> (raw)
In-Reply-To: <20080109003307.GS29972@genesis.frugalware.org>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
Am Mittwoch, 9. Januar 2008 01:33:07 schrieb Miklos Vajna:
> On Tue, Jan 08, 2008 at 11:25:45PM +0100, Dennis Schridde
<devurandom@gmx.net> wrote:
> > mkdir org.gna.warzone2100.git
> > cd org.gna.warzone2100.git
> > git --bare init
> > git --bare svn init --use-svnsync-props --stdlayout
> > file:///var/svn/warzone2100/
> > git --bare svn fetch
>
> wget http://svn.kynes.de/warzone2100.bz2
>
> svnadmin create warzone2100 && bzcat warzone2100.bz2 | svnadmin load
> warzone2100
>
> the rest is the same i get a segfault at the very same place.
>
> > If I do not specify --use-svnsync-prop to "git svn init", it gets past
> > r13 in tags/1.10a.
>
> same.
>
> > I am using these versions:
> > svn, version 1.4.6 (r28521)
> > git version 1.5.4.rc2
>
> $ svn --version
> svn, version 1.4.5 (r25188)
>
> $ git --version
> git version 1.5.4.rc2.38.gd6da3
Same with git version 1.5.3.7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-01-09 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 22:25 git svn fetch segfaults Dennis Schridde
2008-01-09 0:33 ` Miklos Vajna
2008-01-09 12:53 ` Dennis Schridde [this message]
2008-01-09 20:14 ` Junio C Hamano
2008-01-09 20:53 ` Björn Steinbrink
2008-01-09 22:15 ` Björn Steinbrink
2008-01-10 1:45 ` Dennis Schridde
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=200801091353.44630.devurandom@gmx.net \
--to=devurandom@gmx.net \
--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;
as well as URLs for NNTP newsgroup(s).