This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4B01AB601F0A57F58CA358F1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
If memory serves me right, Poul-Henning Kamp wrote:
> I just noticed that the hardware notes contain three empty sections
> for TR, FDDI and ATM interfaces:
>=20
> http://localhost:8080/releases/6.1R/hardware-amd64.html#FDDI
>=20
> Is this intentional/optimal/old cruft ?
Some combination of the first and the last.
It's an artifact of the (stupid) way that I tried to generate separate
hardware note documents for each architecture. When I first did this
work, we only supported i386 and alpha, but the way we do conditional
inclusion of text just doesn't scale very well to the number of
architectures we have.
I am leaning towards the idea that the right way to do this now is to
have unified, mostly-MI release documentation (i.e. release notes,
hardware notes, installation guide) annotated appropriately in the
places that need to be MD.
Bruce.
--------------enig4B01AB601F0A57F58CA358F1
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.3 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEjvFZ2MoxcVugUsMRAgcgAKCCsk6LkUbOLC7JsiaAwADNwkuS+gCgjlgC
esBiEGLzVhfFQfMnGUIFaF8=
=KBRY
-----END PGP SIGNATURE-----
--------------enig4B01AB601F0A57F58CA358F1--