Re: git svn clone segmentation faul issue
- From
- Eric Wong <e@80x24.org>
- Date
- Jun 28, 2016, 19:48 UTC
- Message-ID
- <20160628194804.GA3653@dcvr.yhbt.net>
- In-Reply-To
- <0BCA1E695085C645B9CD4A27DD59F6FA39AAD5CF@GBWGCEUHUBD0101.rbsres07.net>
Ioannis.Kappas@rbs.com wrote:
Show 9 quoted lines
> 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.