From owner-freebsd-current@FreeBSD.ORG Tue Apr 22 20:05:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4628B37B401 for ; Tue, 22 Apr 2003 20:05:49 -0700 (PDT) Received: from wabakimi.chat.carleton.ca (wabakimi.chat.carleton.ca [134.117.1.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3F7343FBD for ; Tue, 22 Apr 2003 20:05:48 -0700 (PDT) (envelope-from creyenga@connectmail.carleton.ca) Received: from fireball (resnet-93-187.cavern.carleton.ca [134.117.93.187]) h3N35fC7014418; Tue, 22 Apr 2003 23:05:41 -0400 (EDT) Message-ID: <001301c30945$32ae1a10$0200000a@fireball> From: "Craig Reyenga" To: "David Leimbach" References: Date: Tue, 22 Apr 2003 23:05:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 cc: freebsd-current@freebsd.org Subject: Re: Makefile in /usr/src/lib/libdisk WARNS change? PLEASE READ! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2003 03:05:50 -0000 From: "David Leimbach" > > On Tuesday, April 22, 2003, at 09:53 PM, Craig Reyenga wrote: > > >> Hi, > >> > >> I posted the libdisk patch that was heavily ignored two days ago :). [BIG SNIP] > > I know how you feel, boss. I just started a thread about how my > > computer > > dies if I run out of memory, and all I got was a "me too" from another > > fellow user. No developers jumped in. It seems like unless you have a > > LOR or > > a laptop, you get no attention. And no, don't bother filing a bug > > report > > because it will stagnate further. > > > > Craig, > > I don't mean to imply the developers aren't doing their damnedest to > make things > work but if they can't verify our bug reports they won't do a thing > about it and > rightly so... How would they know if it was ever fixed if they can't > see the problem > :). > > I don't want to be an ass about it but I felt I had to explain the > situation further. > > I mean if everyone were experiencing my situation this wouldn't be an > issue. So what > I would like is either of > > a) someone to commit the patch or find a better fix. > or > b) tell me what's wrong with my process or help me debug my process > of building FBSD-CURRENT. > > Everything else seems to work fine! :) > Dave True story. I guess I'm over-reacting, but it can get to be very frustrating. I guess we can't expect hand-and-foot support from people we don't even know. Anyways, hopefully your patch makes it, and more bugs get sprayed before 5.1. -Craig