git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: Windows Bluescreen

From
Jason Pyeron <jpyeron@pdinc.us>
Date
Feb 12, 2015, 12:53 UTC
Message-ID
<6CEE72C927ED42B4A834612538B22F5D@black>
In-Reply-To
<CAEuupiuv=gRnnZm1C75dx35nC=sXR1Hb_PzLXzAKHwaD7kYsXA@mail.gmail.com>
Show 10 quoted lines
> -----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.
Show 39 quoted lines
> 
> 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.
Previous: Thomas Braun
Message 11 of 11 in “Windows Bluescreen”
  1. erik@aercon.netFeb 9, 2015
  2. Chris PackhamFeb 11, 2015
  3. Erik FriesenFeb 11, 2015
  4. Chris PackhamFeb 12, 2015
  5. Erik FriesenFeb 12, 2015
  6. Erik FriesenFeb 12, 2015
  7. Thomas BraunFeb 12, 2015
  8. Erik FriesenFeb 12, 2015
  9. Yue Lin HoFeb 12, 2015
  10. Thomas BraunFeb 13, 2015
  11. Jason PyeronFeb 12, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.