Date: Mon, 24 Jan 2000 15:33:06 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: 4.0 CODE FREEZE vs patches to lpr/lpc Message-ID: <200001242333.PAA93308@apollo.backplane.com> References: <Pine.BSF.4.21.0001241144120.79253-100000@hub.freebsd.org> <v04210100b4b2723017bb@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
:Could someone commit the 2-line bug fix in bin/15728 before yet
:another system release goes out the door?
Done!
: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
If it is a very simple and obvious change you can typically email one
of the committers specifically and he will do it. E.G. you could just
email me and I'd do it.
If it's more complex then the best way to go is to get the PR assigned
to a committer somehow (the 'Assigned' field). This is one of the main
deficiencies of the PR system --- PR's are not automatically assigned
to committers based on criterea (such as the module or subsystem).
-Matt
Matthew Dillon
<dillon@backplane.com>
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?200001242333.PAA93308>