Date: Tue, 21 Nov 2006 18:44:17 +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: <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> In-Reply-To: <20061121040153.GA17933@tomcat.kitchenlab.org> References: <20061121040153.GA17933@tomcat.kitchenlab.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--EuxKj2iCbKjpUGkD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 20, 2006 at 08:01:53PM -0800, Bruce A. Mah wrote: [...] >=20 > 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: >=20 > [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: [i386] Some sentence applying only to i386. [amd64] Some sentence applying only to amd64. [arm] Some sentence applying only to arm. [sparc64] Some sentence applying only to sparc64. [i386] Some sentence applying only to i386. 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? OTOH, maybe I've just completely misunderstood you :-) > (As a point of reference, the main part of the release notes on HEAD, > new.sgml, contains 353 <para> elements, of which 27 have MD "arch=3D" > properties So more than 90% of the paragraphs in the release notes > are common to all architectures anyway.) >=20 > I want to start first with the release notes because this change would > be the most straight-forward for that document. The hardware list is > similar, although it has MD sections of text that would need to be > organized into some reasonable document structure. I think that the > install guide really needs to be rewritten; I actually have some work > from a few years ago in this direction that gave me the idea for MI > release documentation in the first place. >=20 > Comments? >=20 Apart from the comment above, this sounds like a good idea. - 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 --EuxKj2iCbKjpUGkD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFYzrwbHYXjKDtmC0RAhDhAJ97Xdl14g8Q7QtfVrr0TXUTo8BJ/wCgvrdS MsV9bKST5G2w78H2Ps/CgjE= =jpMV -----END PGP SIGNATURE----- --EuxKj2iCbKjpUGkD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061121174416.GB4192>