From owner-freebsd-current Tue Jan 25 3:48:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id ECEF514EFA; Tue, 25 Jan 2000 03:48:38 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id LAA92194; Tue, 25 Jan 2000 11:48:31 GMT (envelope-from joe) Date: Tue, 25 Jan 2000 11:48:30 +0000 From: Josef Karthauser To: Garance A Drosihn Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: 4.0 CODE FREEZE vs patches to lpr/lpc Message-ID: <20000125114830.E56451@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If it's easy I'll look at it. (I made a commit to lpr myself last week anyway.) Joe On Mon, Jan 24, 2000 at 05:08:56PM -0500, Garance A Drosihn wrote: > >On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > > > > > On the 29th of January, I'll be freezing the -current branch (well, > > > OK, the trunk). That means NO commits without my review first ... > > Could someone commit the 2-line bug fix in bin/15728 before yet > another system release goes out the door? > > Jan 7th, 1999: problem first reported in bin/9362 > Sep 9th, 1999: fix first described (with patch) in bin/13549 > Nov 18th, 1999: fix acknowledged by another person in bin/14975, > although the update there is "backwards" (it would > turn a FIXED source code to become the UNFIXED one, > because it's a 'diff cmds cmds.orig'). > Dec 27th, 1999: slightly prettier version of the Sept 9th patch is > sent in and becomes bin/15728. > > There some other lpr/lpd PR's which look like they should go in, > and I have more lpr/lpd patches to write up sometime, but I figure > if I can't get this damn 2-line fix committed then there isn't > much point pursuing any other printing improvements. It's a > trivial fix to an obvious and 100% reproducible bug, and yet it > just sits there. Note this is not the somewhat more controversial > change (to 'lpr -r') that I was pursuing earlier this month, as it > might be a bit too close to the code freeze to put that one in. > > Given that lpr/lpd seems to be very low priority in most committers > queues, is there any way to expedite changes like these? I'm > trying avoid any ranting or raving, but this has been pretty > exasperating. > > > --- > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > Senior Systems Programmer or drosih@rpi.edu > Rensselaer Polytechnic Institute -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message