Date: Mon, 27 Mar 2000 11:22:42 -0700 From: Warner Losh <imp@village.org> To: Sheldon Hearn <sheldonh@uunet.co.za> Cc: current@FreeBSD.ORG Subject: Re: questions asked in CURRENT, answered in UPDATING Message-ID: <200003271822.LAA94849@harmony.village.org> In-Reply-To: Your message of "Mon, 27 Mar 2000 14:01:53 %2B0200." <54598.954158513@axl.ops.uunet.co.za> References: <54598.954158513@axl.ops.uunet.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <54598.954158513@axl.ops.uunet.co.za> Sheldon Hearn writes: : I'd like to propose that everyone confine such answers to private mail. No. I'm going to continue to do it publicly. : 1) Folks who _do_ read UPDATING aren't further inconvenienced by : multiple "see UPDATING" replies. 'd' works well :-). I keep the messages short, and to the point. : 2) Instead, the folks who didn't read UPDATING suffer this : inconvenience. It's an excellent learning opportunity for these : people, since multiple "see UPDATING" replies are likely to help them : remember for next time. This would be true a higher percentage of people were actually reading UPDATING before posting. Seeing a simple "See UPDATING: XXXX" keeps the file in the public eye and thus encourages people to look there and let me know when things are wrong. It also tends to self regulate the UPDATING usage. As usage falls, more messages are likely to appear on the list, to which the see updating replies happen, which causes usage to rise again. : This is akin to jmb's preference for allowing misdirected subscribe : and unsubscribe requests onto the list. ;-) : : You like? Yes? No? I don't like. Warner 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?200003271822.LAA94849>