X-Spam-Check-By: sourceware.org Date: Mon, 24 Jul 2006 14:42:40 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Why are Windows paths broken in make 3.81? Message-ID: <20060724184240.GB21218@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <9c2aabaf0607211629u4e29ffa1w5f09b3d8e5a923fc AT mail DOT gmail DOT com> <44C1796F DOT 50308 AT netacquire DOT com> <20060722222244 DOT GB18054 AT trixie DOT casa DOT cgf DOT cx> <44C4FF71 DOT 6050505 AT netacquire DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44C4FF71.6050505@netacquire.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Jul 24, 2006 at 10:12:17AM -0700, Joachim Achtzehnter wrote: >Christopher Faylor wrote: >>On Fri, Jul 21, 2006 at 06:03:43PM -0700, Joachim Achtzehnter wrote: >>>There was also some difference in newline handling which required >>>another set of sed changes, arghh! >> >>Well with detailed bug reports like this and the previous "make >>provides an error on one of my complex makefiles" we're surely well on >>the road towards perfection. > >This sarcastic response to one sentence out of a much longer post >quoted in isolation suggests that a clarification is in order. Neither >of my previous posts, not the one about the "threadlist_ix -1" error >and not the one I wrote specifically in response to a claim that the >recent changes to make were "not an inconvenience", were written with >any expectations for a fix. Well, you *could* expect a fix if you provided enough details. It is pretty frustrating to see content-free bug reports like "there was also some difference in newline handling" or "My big/complicated makefile SEGVs". Whether you intended these as bug reports or not, they are still reports of problems and no package maintainer wants to see reported problems sent to thousand of people whether they were just intended to blow off steam or not. cgf -- 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/