All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Ioannis.Kappas@rbs.com
Cc: git@vger.kernel.org
Subject: Re: git svn clone segmentation faul issue
Date: Tue, 28 Jun 2016 19:48:04 +0000	[thread overview]
Message-ID: <20160628194804.GA3653@dcvr.yhbt.net> (raw)
In-Reply-To: <0BCA1E695085C645B9CD4A27DD59F6FA39AAD5CF@GBWGCEUHUBD0101.rbsres07.net>

Ioannis.Kappas@rbs.com wrote:
> Fortunately, a patch has already been submitted to subversion
> with (github) revision
> a074af86c8764404b28ce99d0bedcb668a321408 (at
> https://github.com/apache/subversion/commit/a074af86c8764404b28ce99d0bedcb668a321408
> ) on the trunk to handle this and a couple of other similar
> cases. But by the looks of it has not been picked up yet in
> the latest subversion 1.9.4 release or the 1.9.x branch,
> perhaps because this patch was identified in sanity checks
> rather than coming out from a perceivable production issue?

Thank you for documenting this.  Curious, does this affect older
SVN versions or only 1.9.x?

I don't know Perl internals well or SWIG at all; so reports
like these are very much appreciated.

  parent reply	other threads:[~2016-06-28 19:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  8:50 git svn clone segmentation faul issue Ioannis.Kappas
2016-06-28 11:47 ` Johannes Schindelin
2016-06-28 13:32   ` Johannes Schindelin
2016-06-28 16:13     ` Ioannis Kappas
2016-06-28 16:27       ` Johannes Schindelin
2016-06-29  7:13         ` Johannes Schindelin
2016-06-29  9:00           ` Ioannis Kappas
2016-06-29 11:43             ` Johannes Schindelin
2016-07-01 10:09               ` Ioannis Kappas
2016-07-01 13:41                 ` Johannes Schindelin
2016-06-28 19:48 ` Eric Wong [this message]
2016-06-29  8:11   ` Ioannis Kappas

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=20160628194804.GA3653@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=Ioannis.Kappas@rbs.com \
    --cc=git@vger.kernel.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 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.