From owner-freebsd-current@FreeBSD.ORG Sat Jan 24 04:37:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3324D16A4CE for ; Sat, 24 Jan 2004 04:37:22 -0800 (PST) Received: from arthur.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 193D743D2F for ; Sat, 24 Jan 2004 04:37:18 -0800 (PST) (envelope-from simon@arthur.nitro.dk) Received: by arthur.nitro.dk (Postfix, from userid 3000) id E032C1142B; Sat, 24 Jan 2004 13:37:15 +0100 (CET) Date: Sat, 24 Jan 2004 13:37:15 +0100 From: "Simon L. Nielsen" To: current@freebsd.org, sagejona@theatre.msu.edu Message-ID: <20040124123708.GA794@arthur.nitro.dk> References: <20040124070846.GA595@omoikane.mb.skyweb.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: <20040124070846.GA595@omoikane.mb.skyweb.ca> User-Agent: Mutt/1.5.5.1i Subject: Re: RFC: Weekly status update 17/01/04-23/01/04 (cvs-src summary) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2004 12:37:22 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.01.24 01:08:46 -0600, Mark Johnston wrote: > If you have a minute, please read through this message and give me a > sense of what you think. In particular, please think about: >=20 > - Subject matter - too narrow? too broad? should I cover the -current > list instead of cvs-src, or try to combine both into one report? While it would be nice to cover -current also, I think just cvs-src is fine. -current gets a very large amount of emails, so if -current is included in the summarary I think there is the risk that the report puts too large a workload on the author. > - Prose - too technical? not technical enough? too flowery? too plain? I think it was fine, it covered the important points without going into uneeded details. > - Commits covered - Did I miss anything I should have included, or > include things I should have skipped? I read the source commit mails, and I can't remember any important subjects which has been missed. > - Impartial? I've tried not to attribute consensus and opinions where > they weren't very clear; have I succeeded? I think that was very successful. Especially the 'Filenames and line numbers added to panic output' debate got a bit heated, and I think you described it very impartial (and only the important points). > - Interest - would you be interested in seeing something like this > produced weekly? Defiantly. Nice work! (especially doing it and not just talking about doing it :-) ). --=20 Simon L. Nielsen FreeBSD Documentation Team --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAEmb0h9pcDSc1mlERArZtAKDFE4NMBxfziDZJnmOY0CEkMLxxFgCfasVV WAJPbJZOk+ZLr9s6bw7yJho= =9zAF -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--