From owner-freebsd-doc@FreeBSD.ORG Wed Nov 22 16:29:36 2006 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F72D16A4B3; Wed, 22 Nov 2006 16:29:36 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id B993543D8B; Wed, 22 Nov 2006 16:28:26 +0000 (GMT) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from circe ([134.130.3.36]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0J9500E714G2OF50@mta-1.ms.rz.RWTH-Aachen.de>; Wed, 22 Nov 2006 17:28:50 +0100 (CET) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Wed, 22 Nov 2006 17:28:50 +0100 (MET) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.8/8.13.1/1) with ESMTP id kAMGSmad023313; Wed, 22 Nov 2006 17:28:48 +0100 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1Gmuxt-0002Pq-Te; Wed, 22 Nov 2006 17:28:49 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 410AD3F41E; Wed, 22 Nov 2006 17:28:49 +0100 (CET) Date: Wed, 22 Nov 2006 17:28:49 +0100 From: Christian Brueffer In-reply-to: <45634E53.1020609@freebsd.org> To: "Bruce A. Mah" Message-id: <20061122162848.GC2043@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=9Ek0hoCL9XbhcSqy Content-disposition: inline X-Operating-System: FreeBSD 6.2-PRERELEASE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> <45634E53.1020609@freebsd.org> User-Agent: Mutt/1.5.11 Cc: freebsd-doc@freebsd.org Subject: Re: RFC: Release notes rearrangement X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 16:29:36 -0000 --9Ek0hoCL9XbhcSqy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 21, 2006 at 11:06:59AM -0800, Bruce A. Mah wrote: > If memory serves me right, Christian Brueffer wrote: > > On Mon, Nov 20, 2006 at 08:01:53PM -0800, Bruce A. Mah wrote: > > [...] > >> To address these problems I'd like to collapse all of the MD documents > >> into a single set of MI documents. For paragraphs (sections, > >> whatever) that only apply to given architectures, we'd simply add > >> in-line text indicating this, something like: > >> > >> [i386] Some sentence applying only to i386. > >> > >=20 > > Hmm, what I like about the current notes is that if I'm only interested > > in on arch, I just get the stuff that concerns this specific arch. From > > what you describe here it sounds like this: > >=20 > > [i386] Some sentence applying only to i386. > >=20 > > [amd64] Some sentence applying only to amd64. > >=20 > > [arm] Some sentence applying only to arm. > >=20 > > [sparc64] Some sentence applying only to sparc64. > >=20 > > [i386] Some sentence applying only to i386. > >=20 > > Of course many items are general, but I think we want to avoid clutter > > like this. Do you have something in mind for this? Maybe put all the > > arch specific stuff in special arch sections below all the generic > > stuff? > >=20 > > OTOH, maybe I've just completely misunderstood you :-) >=20 > Hey Christian-- >=20 > You understood me correctly I think! Remember that only a small > fraction (< 10%) of paragraphs in HEAD's release notes have this > property, so I don't think that things will be really cluttered. >=20 > On HEAD: >=20 > tomcat:common% grep ' 380 2598 24637 > tomcat:common% grep ' 27 179 1852 >=20 > On RELENG_6_2 (this is just an example of what a more "typical" release > would look like...I don't intend): >=20 > tomcat:common% grep ' 111 780 7068 > tomcat:common% grep ' 7 50 478 >=20 > Maybe I should try to mock this up so we're thinking about the same thing? >=20 Ok, I assume you have a prototype in the works. When that's out, we can still decide whether or not this is an issue. Let's see how it looks :-) - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --9Ek0hoCL9XbhcSqy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFZHrAbHYXjKDtmC0RAvI5AJ4jVNzX5XPp+p8Hj2fyWZPpbGwnhACfSuSl OxHMAf0Mti1HtD/Tq4SSC80= =rO+y -----END PGP SIGNATURE----- --9Ek0hoCL9XbhcSqy--