Date: Sat, 1 Jun 2002 15:04:29 -0400 From: "Shadow-Cat" <Shadow-Cat@sympatico.ca> To: <freebsd-bugbusters@FreeBSD.org> Subject: PR ...? No, NO, bad idea, that, ...! Message-ID: <000801c2099f$28a44720$0c94fea9@oemcomputer>
index | next in thread | raw e-mail
[-- Attachment #1 --] - June 01st. 2002 - Maybe you ought to choose a better name than PR which is more often a reference to Public Relationships. on a corporate level. PR is lible to cause much confussion.? These guidelines describe recommended handling practices for FreeBSD Problem Reports (PRs). Whilst developed for the FreeBSD PR Database Maintenance Team <freebsd-bugbusters@FreeBSD.org>, these guidelines should be followed by anyone working with FreeBSD PRs. [-- Attachment #2 --] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2715.400" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>- June 01st. 2002 - </FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2> Maybe you ought to choose a better name than PR which is more often a reference to Public Relationships. on a corporate level. PR is lible to cause much confussion.? </FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2> <P>These guidelines describe recommended handling practices for FreeBSD Problem Reports (PRs). Whilst developed for the FreeBSD PR Database Maintenance Team <TT class=EMAIL><<A href="mailto:freebsd-bugbusters@FreeBSD.org">freebsd-bugbusters@FreeBSD.org</A>></TT>, these guidelines should be followed by anyone working with FreeBSD PRs.</P></FONT></DIV></BODY></HTML>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000801c2099f$28a44720$0c94fea9>