[OpenAFS] New OpenAFS website proposal.

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigD3723CDD33F0272A5A943650
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/7/2010 12:59 PM, Derrick Brashear wrote:
> Probably the tool that "emits" the documentation from git should write =
a
> correct revision table, and in this vein we illustrate some of the tool=
 smithing
> we need.

I wrote script appropriate to build the OpenAFS release number into the
revision table.

  http://docs.openafs.org/UserGuide/index.html
  http://docs.openafs.org/AdminGuide/index.html
  http://docs.openafs.org/QuickStartUnix/index.html

Exporting the git revision info for a directory would be a nice touch
though.  However, as things stand today it should be possible to see
what release the documentation came from.

Jeffrey Altman


--------------enigD3723CDD33F0272A5A943650
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.9 (MingW32)

iQEcBAEBAgAGBQJNAVukAAoJENxm1CNJffh4S7oIALoHIVjwm2Rv4X/cAuDBprrj
dK7zkWXyNu9Olrtz7lcm3DVq+3/+h3Nunzybcp8tv/KPcUwz7b/0F5MgqmVGquGZ
kSXSGyLv+aGHjiCQ2n0BpXZ/8/keJVmnst19r4dTBb7xmXklOIl6l7djSS7ULIzZ
plOge70hrO2yFJidkR/wjiMAgPlzLhaZ20PDxiN7RXbldZlzt2KWpTLhjEeXAt/H
6u5eMUDq5l21ET5Yj7LrllYHdK5/ug2Eaz4QD9QwyYfhIqYXxHXHLZVHbPD3w6Xa
pFRLmOjQTrnQiNavSye4OGQUUYYSV0EIC0vjIXYzfUAT+QavAD2K1zNuiEDav4g=
=0Q33
-----END PGP SIGNATURE-----

--------------enigD3723CDD33F0272A5A943650--