[OpenAFS-devel] Doxygen

[Jeffrey Altman]

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

On 9/16/2012 5:42 PM, Russ Allbery wrote:
> Jason Edgecombe <jason@rampaginggeek.com> writes:
>=20
>> Do we need one unified doxygen build for src and doc, or split them up=
 as
>> separate runs of doxygen?
>=20
>> In other words, what should the final output look like?
>=20
> I think it should be unified.  In the long run, I think that the files =
in
> doc should be moved into somewhere reasonable in the source tree to mak=
e
> it easier to do a complete Doxygen run.


The protocol docs are a replacement for the files in doc/pdf that were
originally written back in the early 90s.   There is a reasonable
argument to be made that since the protocol is independent of the
OpenAFS implementation that it should be built separately.

The architecture docs I agree should be moved into the src tree so that
they can be more easily built into the same output document as the rest
of the source documentation.

Feel free to submit a patch that makes that happen once you figure out
what works best.

Jeffrey Altman



--------------enig1E7E35FB9CCC3386A9DE94E2
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)

iQEcBAEBAgAGBQJQVnhXAAoJENxm1CNJffh4MpQIAJNHsm1VONG5LHD/1gf+SIR+
OOKChpuLsrTAfJU3Vk6DMz4txA/sZsbrXon0Uwuft8sNpSxnsy5xyXhorQ/soRvi
yKv5NsrqYYSRnJCTpNSGYyNFxxlR8jYIHxRpUmkB2obXerBZ0PfKz8WkT1uPpVI/
VkZdPqZLhiW3WEOMEB8q39g9ijhnaUa2kniOQSWicLNBU74K8noEx1T8L1UPnf9S
41jFUtDrlT7mWoc6kL6oUJjoqn43/+qoiGJjsFPT2O8pQ3hJ2MlZKObxIImOW+gq
NnvLBHyse6HPEKakPS/QOiKRtG0VfkWzGDAQG693YMUdNCBbYvaqHe2BLgZ+r7Q=
=4L9J
-----END PGP SIGNATURE-----

--------------enig1E7E35FB9CCC3386A9DE94E2--