From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "'Erik Friesen'" <erik@aercon.net>,
"'Chris Packham'" <judge.packham@gmail.com>
Cc: "'GIT'" <git@vger.kernel.org>, <msysgit@googlegroups.com>
Subject: RE: Windows Bluescreen
Date: Thu, 12 Feb 2015 07:53:44 -0500 [thread overview]
Message-ID: <6CEE72C927ED42B4A834612538B22F5D@black> (raw)
In-Reply-To: <CAEuupiuv=gRnnZm1C75dx35nC=sXR1Hb_PzLXzAKHwaD7kYsXA@mail.gmail.com>
> -----Original Message-----
> From: Erik Friesen
> Sent: Thursday, February 12, 2015 7:22
>
> 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.
FWIW, if it does not get fixed you can use the cygwin git and openssh without many problems, and the cygwin group is pretty responsive to issues like this.
>
> 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.
>
> On Thu, Feb 12, 2015 at 4:33 AM, Chris Packham
> <judge.packham@gmail.com> wrote:
> > On Thu, Feb 12, 2015 at 1:33 AM, Erik Friesen
> <erik@aercon.net> wrote:
> >> Pushing over http and https are unaffected.. My linux nas
> died, so on
> >> rebuild I tried to do the ssh thing, and realized quite soon that
> >> things weren't right.
> >>
> >> As far as other uses of ssh, I don't know, I use putty
> frequently, but
> >> I am not clear if it is using the same libraries or not.
> >
> > I think putty ships it's own ssh implementation rather than using an
> > openSSH port.
> >
> >> I hunted around for the bugreport email on mysgit but
> couldn't seem to
> >> find it. It seems in the foggy recesses I remember
> reading about an
> >> ssh issue with windows, but can't find it now.
> >>
> >
> > https://github.com/msysgit/git/issues
> >
> > Happy hunting :). Actually if it is a ssh problem it might be a
> > generic MSYS issue. So there's another bug tracker to look through
> >
> > http://sourceforge.net/p/mingw/bugs/
> >
> >
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
prev parent reply other threads:[~2015-02-12 12:53 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
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 [this message]
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=6CEE72C927ED42B4A834612538B22F5D@black \
--to=jpyeron@pdinc.us \
--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