Date: Tue, 21 Nov 2006 11:06:59 -0800 From: "Bruce A. Mah" <bmah@freebsd.org> To: Christian Brueffer <brueffer@freebsd.org> Cc: freebsd-doc@freebsd.org Subject: Re: RFC: Release notes rearrangement Message-ID: <45634E53.1020609@freebsd.org> In-Reply-To: <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE> References: <20061121040153.GA17933@tomcat.kitchenlab.org> <20061121174416.GB4192@haakonia.hitnet.RWTH-Aachen.DE>
next in thread | previous in thread | raw e-mail | index | archive | help
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 '<para' new.sgml | wc
380 2598 24637
tomcat:common% grep '<para arch=3D' new.sgml | wc
27 179 1852
On RELENG_6_2 (this is just an example of what a more "typical" release
would look like...I don't intend):
tomcat:common% grep '<para' new.sgml | wc
111 780 7068
tomcat:common% grep '<para arch=3D' new.sgml | wc
7 50 478
Maybe I should try to mock this up so we're thinking about the same thing=
?
Bruce.
--------------enigD5D03B7DB1007B6256BA4761
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFY05T2MoxcVugUsMRAk3fAKCOqNLUCoTegni/bEbG/IDXJTKc5QCeOWYC
jsh7qUEcD6PizMZvb41wPvk=
=mBv3
-----END PGP SIGNATURE-----
--------------enigD5D03B7DB1007B6256BA4761--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45634E53.1020609>