Skip Menu |
 

From: kaduk@MIT.EDU
Subject: SVN Commit

Better names for doxygen-Sphinx bridge functions

It is confusing when the codepath for the production doc build
involves calling functions with names like "test". Rename things
which are in active use so that routines which are actually only
used for testing are more discernable as such.

https://github.com/krb5/krb5/commit/060b1eb1e38b294495adab784da32ca4e9871d20
Author: Ben Kaduk <kaduk@mit.edu>
Commit: 060b1eb1e38b294495adab784da32ca4e9871d20
Branch: master
doc/tools/doxy.py | 8 ++++----
doc/tools/doxybuilder_funcs.py | 19 ++++++++-----------
doc/tools/doxybuilder_types.py | 20 ++++++++++----------
3 files changed, 22 insertions(+), 25 deletions(-)
From: tlyu@mit.edu
Subject: SVN Commit

Better names for doxygen-Sphinx bridge functions

It is confusing when the codepath for the production doc build
involves calling functions with names like "test". Rename things
which are in active use so that routines which are actually only
used for testing are more discernable as such.

(cherry picked from commit 060b1eb1e38b294495adab784da32ca4e9871d20)

https://github.com/krb5/krb5/commit/a30408bf668d028f4172124ec2307eec58829f3a
Author: Ben Kaduk <kaduk@mit.edu>
Committer: Tom Yu <tlyu@mit.edu>
Commit: a30408bf668d028f4172124ec2307eec58829f3a
Branch: krb5-1.11
doc/tools/doxy.py | 8 ++++----
doc/tools/doxybuilder_funcs.py | 19 ++++++++-----------
doc/tools/doxybuilder_types.py | 20 ++++++++++----------
3 files changed, 22 insertions(+), 25 deletions(-)