From: Eric Wong <normalperson@yhbt.net>
To: Steven Grimm <koreth@midwinter.com>
Cc: git@vger.kernel.org
Subject: [RFH] Re: Segmentation fault in git-svn
Date: Thu, 19 Apr 2007 14:31:12 -0700 [thread overview]
Message-ID: <20070419213112.GA24780@muzzle> (raw)
In-Reply-To: <20070418090143.GA11894@muzzle>
Eric Wong <normalperson@yhbt.net> wrote:
> Eric Wong <normalperson@yhbt.net> wrote:
> The verdict is still out on all patches and attempts I've posted
> to fix the segfault. I'm quite busy at the moment and won't
> be attending to git-svn things for another few days.
Ok, those didn't work. I'm still preoccupied with another project
that has a higher priority; and I've come down with a cold so
if anybody else wants to step up to the plate, please take a stab
at it.
This issue has NOT been known to cause data corruption from any
users that experienced it[1]. It seems to be happening
in between when changesets are actually fetched.
[1] - if there is any corruption to a particular file, it'll
trigger an MD5 mismatch the next time that file is updated.
--
Eric Wong
next prev parent reply other threads:[~2007-04-19 21:31 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 ` Eric Wong [this message]
2007-05-03 12:35 ` Peter Baumann
2007-05-13 8:21 ` Eric Wong
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=20070419213112.GA24780@muzzle \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.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.