From: Thomas Braun <thomas.braun@virtuell-zuhause.de>
To: Erik Friesen <erik@aercon.net>
Cc: Chris Packham <judge.packham@gmail.com>,
GIT <git@vger.kernel.org>,
msysgit@googlegroups.com
Subject: Re: Re: Windows Bluescreen
Date: Thu, 12 Feb 2015 13:42:39 +0100 [thread overview]
Message-ID: <1423744959.10453.3.camel@thomas-debian-x64> (raw)
In-Reply-To: <CAEuupiuv=gRnnZm1C75dx35nC=sXR1Hb_PzLXzAKHwaD7kYsXA@mail.gmail.com>
Am Donnerstag, den 12.02.2015, 07:21 -0500 schrieb Erik Friesen:
> I'd say this is related. http://sourceforge.net/p/mingw/bugs/2240/
>
> There isn't much hope, that was filed months ago with no action. I
> suggest moving to another ssh library perhaps? Anyways, this is a
> windows git bug report, so it really needs to stay with mysgit in my
> opinion.
>
> I'd say it should reproduce without much effort. Do a git push using
> win7 64 pro or similar, I'd say it will have issues.
>
> At minimum, this should be on the list for others to view. I have run
> across problems from others, but I don't think they realized it could
> be an ssh problem.
(Please don't TOP post)
The cited bug report does not correlate to msysgit as we compile and
ship our own openssh.
Git for Windows Version 1.8.x might still have the old and slow openssh.
With the newest version I get speeds of up to 30MB/s over Gigabit LAN.
Can you create a minimal test case to reprocude the problem?
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2015-02-12 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 20:12 Windows Bluescreen erik
2015-02-11 8:56 ` Chris Packham
2015-02-11 12:33 ` Erik Friesen
2015-02-12 9:33 ` Chris Packham
2015-02-12 12:21 ` Erik Friesen
2015-02-12 12:25 ` Erik Friesen
2015-02-12 12:42 ` Thomas Braun [this message]
2015-02-12 13:21 ` Erik Friesen
2015-02-12 13:48 ` Yue Lin Ho
2015-02-13 21:09 ` Thomas Braun
2015-02-12 12:53 ` Jason Pyeron
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=1423744959.10453.3.camel@thomas-debian-x64 \
--to=thomas.braun@virtuell-zuhause.de \
--cc=erik@aercon.net \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.com \
--cc=msysgit@googlegroups.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).