Date: Thu, 2 Dec 1999 17:06:03 -0500 (EST) From: Matt Behrens <matt@zigg.com> To: "Jung, Michael" <mjung@npc.net> Cc: "'Wes Peters'" <wes@softweyr.com>, "'Steve Reid'" <sreid@sea-to-sky.net>, "'Sheldon Hearn'" <sheldonh@uunet.co.za>, "'Bill Swingle'" <unfurl@dub.net>, "'security@FreeBSD.ORG'" <security@FreeBSD.ORG>, "'Jordan Hubbard'" <jkh@FreeBSD.ORG> Subject: RE: [btellier@USA.NET: Several FreeBSD-3.3 vulnerabilities] Message-ID: <Pine.BSF.4.21.9912021704130.90115-100000@megaweapon.zigg.com> In-Reply-To: <c=US%a=_%p=Financial_Allian%l=EXCHANGE-991202215233Z-9345@exchange.finall.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Today, Jung, Michael wrote: : Why not just have the PR system email the ORIGINATOR when : the PR is closed? : : This way the originator is informed of the update and it's give them : the opportunity to make sure the problem is really resolved. : : At our organization the ORIGINATOR actually receives email : any time the status changes on a ticket. Call me crazy, but I think this happens. (Geeze, I've submitted so many but my memory is failing me...) :-) I like Wes's idea, with one caveat: there are quite a few PRs that are silly -- ones that are really pleas for support. There should ideally be some kind of fallback closing method for those. I know Bugzilla has the ``WORKSFORME'' state which might be useful. Matt Behrens <matt@zigg.com> Owner/Administrator, zigg.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.9912021704130.90115-100000>