Re: [msysGit] Re: Windows Bluescreen

2015-02-13 Thread Thomas Braun
Am 12.02.2015 um 14:21 schrieb Erik Friesen:
 Sorry, I don't know what this TOP posting problem is, and hitting
 reply only replies to the last sender.   If you prefer, and you have
 some regular bugtracker, I could use that instead of email posting.
 
 To repro-
 Set up git user on local linux repo, in my case 192.168.0.100
 
 On a windows 7 64bit machine-
 $ cd myproject
 $ git init
 $ git add .
 $ git commit -m 'initial commit'
 $ git remote add origin git@192.168.0.100:/opt/git/project.git
 $ git push origin master
 (Shamelessly copied from git page)
 
 Problem happens after entering password, it may or may not get started.
 
 The nature of a bluescreen doesn't make debugging and reproduction
 real easy.  If it helps, I can get the dumps from those crashes.  To
 move on, I moved back to local http pushes.

I'm doing pushes over ssh on a daily basis against my linux server.
And I'm using a Win7 64bit machine as well.

Can you try if it makes any difference if you use ssh login with public
keys instead of passwords?

You can also try to add LogLevel Debug to ~/.ssh/config in order to
get more verbose ssh output.


--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [msysGit] Re: Windows Bluescreen

2015-02-12 Thread Erik Friesen
Sorry, I don't know what this TOP posting problem is, and hitting
reply only replies to the last sender.   If you prefer, and you have
some regular bugtracker, I could use that instead of email posting.

To repro-
Set up git user on local linux repo, in my case 192.168.0.100

On a windows 7 64bit machine-
$ cd myproject
$ git init
$ git add .
$ git commit -m 'initial commit'
$ git remote add origin git@192.168.0.100:/opt/git/project.git
$ git push origin master
(Shamelessly copied from git page)

Problem happens after entering password, it may or may not get started.

The nature of a bluescreen doesn't make debugging and reproduction
real easy.  If it helps, I can get the dumps from those crashes.  To
move on, I moved back to local http pushes.

On Thu, Feb 12, 2015 at 7:42 AM, Thomas Braun
thomas.br...@virtuell-zuhause.de wrote:
 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?

--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [msysGit] Re: Windows Bluescreen

2015-02-12 Thread Thomas Braun
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?

--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html