Date: Wed, 10 Dec 2003 09:12:25 -0800 From: bmah@freebsd.org (Bruce A. Mah) To: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) Cc: freebsd-doc@freebsd.org Subject: Re: HEADS UP: doc/ slush Message-ID: <200312101712.hBAHCPO0083022@intruder.kitchenlab.org> In-Reply-To: <xzpiskolilu.fsf@dwp.des.no> References: <200312100457.hBA4vkO0075658@intruder.kitchenlab.org> <xzpy8tklkbx.fsf@dwp.des.no> <200312101629.hBAGTOO0082138@intruder.kitchenlab.org> <xzpiskolilu.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_-1548613775P Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit If memory serves me right, Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= wrote: > bmah@freebsd.org (Bruce A. Mah) writes: > > This affects non-committers as well, in that some people who work on > > translations aren't committers. > > The chances of a heads up getting lost in the noise is much higher on > -doc than on doc-developers. You should at the very least Bcc: > doc-developers on announcements like this. Fine. > > I generally expect that people who do a serious amount of work in doc/ > > are also reading the doc@ list. > > Sure, and src committers read -current, but the code freeze is still > announced on developers (though it should really go to src-developers) This isn't an apt analogy but I'm juggling too many things to get into a debate about this. Thanks, Bruce. --==_Exmh_-1548613775P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) Comment: Exmh version 2.5+ 20020506 iD8DBQE/11P52MoxcVugUsMRAvljAJ9ocGi2/EL13tLCO7TxDoFQuvRetwCeOW4S mE5TDq6jkTSdgy1qKL9ko1I= =ge6x -----END PGP SIGNATURE----- --==_Exmh_-1548613775P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312101712.hBAHCPO0083022>