Date: Wed, 22 Nov 2006 17:28:49 +0100 From: Christian Brueffer <brueffer@FreeBSD.org> To: "Bruce A. Mah" <bmah@freebsd.org> Cc: freebsd-doc@freebsd.org Subject: Re: RFC: Release notes rearrangement Message-ID: <20061122162848.GC2043@haakonia.hitnet.RWTH-Aachen.DE> In-Reply-To: <45634E53.1020609@freebsd.org> References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> <45634E53.1020609@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 '<para' new.sgml | wc > 380 2598 24637 > tomcat:common% grep '<para arch=3D' new.sgml | wc > 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 '<para' new.sgml | wc > 111 780 7068 > tomcat:common% grep '<para arch=3D' new.sgml | wc > 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061122162848.GC2043>