From this thread I gather that little or no progress has been made on addressing the root cause of this issue. It still seems to be broken with the latest 1.7 series packages.
What is the proper method for getting this bug in front of the guys who maintain the openssh package? The cygwin website suggests that the mailing list is the proper channel, but it doesn't seem like anyone's seriously looking into this as an openssh issue. It's clearly affecting more than a few users and the workaround, while reliable, is quite lame. Can this please get a little bit more priority? On Mon, Jan 25, 2010 at 6:17 AM, Andre Loker <lo...@gmx.de> wrote: > alland wrote: >> >> I have the same issue trying to clone a repo with a recently updated >> cygwin. The problem is not present in any other configurations I tried to >> clone >> with, including git/ssh built for MSys on the same computer. >> > > I can confirm the problems myself (cygwin 1.7.1, git 1.6.6.1). Also, using > plink/pageant instead of OpenSSH works as a workaround for me for the > moment, though it's not really convenient. > > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
