From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Ioannis Kappas <ioannis.kappas@rbs.com>
Cc: git@vger.kernel.org
Subject: Re: git svn clone segmentation faul issue
Date: Wed, 29 Jun 2016 13:43:26 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1606291341530.12947@virtualbox> (raw)
In-Reply-To: <loom.20160629T104814-936@post.gmane.org>
Hi Yannis,
On Wed, 29 Jun 2016, Ioannis Kappas wrote:
> Johannes Schindelin <Johannes.Schindelin <at> gmx.de> writes:
>
> > I just re-uploaded new packages, after rebuilding them and making sure
> > that the patch was actually applied.
> >
> > May I ask you to re-test, just to make extra sure that the bug in
> > question is fixed?
>
> I confirm the latest version, built from the 'source files (zip)'
> package, has resolved the issue.
Thank you so much!
> Thanks for the prompt response! Next task is to get the patch through to
> the next subversion official release.
My more immediate concern is MSYS2 (the POSIX-emulating basis of Git for
Windows), and I opened a Pull Request there:
https://github.com/Alexpux/MSYS2-packages/pull/647
If this Pull Request is not picked up in time for the next Git for Windows
version, I plan to use the packages that you tested.
Thanks,
Dscho
next prev parent reply other threads:[~2016-06-29 11:43 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 [this message]
2016-07-01 10:09 ` Ioannis Kappas
2016-07-01 13:41 ` Johannes Schindelin
2016-06-28 19:48 ` Eric Wong
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=alpine.DEB.2.20.1606291341530.12947@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=ioannis.kappas@rbs.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 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).