Respectfully, Doesn't this just push the maintenance effort elsewhere? Suppose the upstream maintainer has "no fun" either?
There are obviously a lot of users in the cygwin community using this feature of cygwin make and would like to see it continue to be supported. Why can't a new maintainer step forward to do so? If the interests of the current maintainer diverge from those of the larger community, then perhaps it's time for the maintainer to consider stepping aside? Again, I'm saying/asking this respectfully. -Brian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Corinna Vinschen Sent: Wednesday, August 16, 2006 10:41 AM To: cygwin@cygwin.com Subject: Re: change in behavior of make from 3.80 to 3.81 > - have the patch made part of the upstream gnu make That's the best solutiion of all. The whole "problem" is that the current Cygwin make maintainer has no fun to work on this issue. Everybody else is free to put a bit of time and sweat into this and get this for free firther on. I'm still wondering why people don't go this way instead of discussing this problem, which is none, IMHO, to death. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/