On 3/11/2010 1:50 PM, Kevin Layer wrote:
Brian L.<br...@blucz.com> wrote:
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?
and another month goes by...
If there is work going on behind the scenes, it would be nice to hear
from the developer(s) working on it.
If it is not being worked on... I agree with Brian. This is a serious
impediment to using Cygwin 1.7. I would think it would be of top
priority.
As always, it's worth noting that one way to jump-start activity in
an area of open source that is of interest to you is dig in and offer
some insights to the problem that's affecting you. I guess this goes
without saying though, sometimes, it's beneficial to say things that
don't need to be said. ;-)
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
