From owner-freebsd-doc@FreeBSD.ORG Tue Nov 21 19:52:33 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 E1C0916A492; Tue, 21 Nov 2006 19:52:33 +0000 (UTC) (envelope-from bmah@freebsd.org) Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id D575C43D5A; Tue, 21 Nov 2006 19:50:19 +0000 (GMT) (envelope-from bmah@freebsd.org) Received: from [192.168.2.119] (hornet.kitchenlab.org [64.142.31.105]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id kALJ6xOX012741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Nov 2006 11:07:00 -0800 Message-ID: <45634E53.1020609@freebsd.org> Date: Tue, 21 Nov 2006 11:06:59 -0800 From: "Bruce A. Mah" User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: Christian Brueffer References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> In-Reply-To: <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD5D03B7DB1007B6256BA4761" 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: Tue, 21 Nov 2006 19:52:34 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD5D03B7DB1007B6256BA4761 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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. Fro= m > 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 :-) Hey Christian-- 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. On HEAD: tomcat:common% grep '