civodul pushed a commit to branch master in repository shepherd. commit 812b2a097873ee36605a0311b730755c0a96f8a8 Author: Ludovic Courtès <l...@gnu.org> Date: Mon Jan 25 23:39:48 2016 +0100
doc: Make the "Internals" section less personal. * shepherd.texi (Internals): Remove the personal introduction. Replace it by a paragraph pointing to mailing lists. (Coding standards): Xref "Coding Style" in Guix. (Design decisions, Runlevel evolution): Add note to mention that it's historical material. --- shepherd.texi | 27 +++++++++++++++++++++------ 1 files changed, 21 insertions(+), 6 deletions(-) diff --git a/shepherd.texi b/shepherd.texi index 74cf584..37aafbe 100644 --- a/shepherd.texi +++ b/shepherd.texi @@ -1140,11 +1140,13 @@ utillity, so it can by used by everyone. This chapter contains information about the design and the implementation details of the Shepherd for people who want to hack it. -If you want your work to get included in the Shepherd, please contact me and -say what you intend to do so that I can give advice on how to do it -and we can avoid duplicating work. My development version is usually -a bit ahead of what I release, as I only want to publish code that got -some testing. + +The GNU@tie{}Shepherd is developed by a group of people in connection +with @uref{https://www.gnu.org/software/guix/, GuixSD}, GNU's advanced +distribution, but it can be used on other distros as well. You're very +much welcome to join us! You can report bugs to +@email{bug-guix@@gnu.org} and send patches or suggestions to +@email{guix-devel@@gnu.org}. @menu * Coding standards:: How to properly hack the Shepherd. @@ -1160,13 +1162,21 @@ some testing. About formatting: Use common sense and GNU Emacs (which actually is the same, of course), and you almost can't get the formatting wrong. -Formatting should be as in Guile and Guix, basically. +Formatting should be as in Guile and Guix, basically. @xref{Coding +Style,,, guix, GNU Guix Reference Manual}, for more info. @c @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @node Design decisions @section Design decisions +@quotation Note +This section was written by Wolfgang Jährling back in 2003 and documents +the original design of what was then known as GNU@tie{}dmd. The main +ideas remain valid but some implementation details and goals have +changed. +@end quotation + The general idea of a service manager that uses dependencies, similar to those of a Makefile, came from the developers of the GNU Hurd, but as few people are satisfied with System V Init, many other people had @@ -1309,6 +1319,11 @@ understand it), you are welcome to do so, of course@dots{} @node Runlevel evolution @section Runlevel evolution +@quotation Note +This section was written by Wolfgang Jährling back in 2003 and is kept +mostly for historians to read. +@end quotation + This section describes how the runlevel concept evolved over time. This is basically a collection of mistakes, but is provided here for your information, and possibly for your amusement, but I'm not sure if