From: Eric Wong <normalperson@yhbt.net>
To: Steven Grimm <koreth@midwinter.com>, git@vger.kernel.org
Cc: Peter Baumann <waste.manager@gmx.de>
Subject: Re: Segmentation fault in git-svn
Date: Sun, 13 May 2007 01:21:19 -0700 [thread overview]
Message-ID: <20070513082118.GC1168@muzzle> (raw)
In-Reply-To: <20070503123512.GA6500@xp.machine.xx>
Peter Baumann <waste.manager@gmx.de> wrote:
> On Mon, Apr 16, 2007 at 03:17:55PM -0700, Steven Grimm wrote:
> > I expect this is really a libsvn bug, but git-svn triggers it, so I'm hoping
> > someone else has run into and solved it, or at least that someone can
> > reproduce it.
> >
> > If I try to clone the "memcached" public repository with the command line
> >
> > git-svn clone --branches=branches --trunk=trunk
> > http://code.sixapart.com/svn/memcached
>
> I'm getting segfaults in git-svn, too.
>
> This command segfaults reproducably in r55 while running
>
> git svn clone svn://svn.berlios.de/vermont vermont \
> -T trunk -b branches -t tags
>
Both repositories seem to be cloning fine after the
patch here:
http://permalink.gmane.org/gmane.comp.version-control.git/47128
I really don't know what's going on with libsvn, either :(
--
Eric Wong
next prev parent reply other threads:[~2007-05-13 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 22:17 Segmentation fault in git-svn Steven Grimm
2007-04-17 9:37 ` Eric Wong
2007-04-17 9:40 ` [PATCH (WIP)] git-svn: cache SVN::Ra functions in a more Perl GC-friendly way Eric Wong
2007-04-24 0:50 ` Steven Grimm
2007-04-25 6:40 ` Eric Wong
2007-04-17 9:55 ` Segmentation fault in git-svn Eric Wong
2007-04-18 9:01 ` Eric Wong
2007-04-19 21:31 ` [RFH] " Eric Wong
2007-05-03 12:35 ` Peter Baumann
2007-05-13 8:21 ` Eric Wong [this message]
2007-05-13 22:04 ` Steven Grimm
2007-05-14 9:02 ` Peter Baumann
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=20070513082118.GC1168@muzzle \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.com \
--cc=waste.manager@gmx.de \
/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).