mirror of
https://github.com/envmodules/modules.git
synced 2026-06-14 00:42:43 +08:00
44c9147ee8
Use inclusive terminology [1] to eliminate 'master' and 'slave' terms as much as possible from code and documentation. 'master' has been changed into 'main' and 'slave' into 'subordinate' or 'sub'. After this change, some references to the 'master' and 'slave' word can still be found in repository: * `slaves` sub-command of `interp` Tcl command * `--slave` option of `update-alternatives tool in RPM spec file * `master_doc` attribute of Sphinx `conf.py` file * git 'master' branch need to be renamed and tools referring it need to be updated accordingly (configure, script/mpub, script/mrel) [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=49decddd39e5f6132ccd7d9fdc3d7c470b0061bb
This file briefly describes the documentation provided here.
readme.txt This file.
example.txt There are lots of things you need to plan out
for a fully functional modules environment.
This document explains some of those details.
source/ Location of the source files used to create
html and man documentation for modules.
If you edit these files run make doc to
rebuild the man and html files.
man/ Location of the man pages generated by make doc
html/ Location of the html pages generated by make doc
howto/ Location of How-to PDF files
paper/ Location of conference paper PDF files
talk/ Location of presentation support PDF files
emacs.txt Hints for using modules with emacs lisp.