Date: Mon, 24 Jan 2000 17:08:56 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: 4.0 CODE FREEZE vs patches to lpr/lpc Message-ID: <v04210100b4b2723017bb@[128.113.24.47]> In-Reply-To: <Pine.BSF.4.21.0001241144120.79253-100000@hub.freebsd.org> References: <Pine.BSF.4.21.0001241144120.79253-100000@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>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
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v04210100b4b2723017bb>