From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 56145@debbugs.gnu.org
Subject: [bug#56145] [PATCH 0/5] Add menus to Services sub-sections
Date: Sun, 03 Jul 2022 12:38:32 +0200 [thread overview]
Message-ID: <874jzy1nx3.fsf_-_@gnu.org> (raw)
In-Reply-To: <201f3aa5e409f45423ec30187f37ee56cc0f7716.1655908912.git.h.goebel@crazy-compilers.com> (Hartmut Goebel's message of "Wed, 22 Jun 2022 17:55:07 +0200")
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> * doc/guix.texi (Services)[Base Services, Networking Setup, Networking
> Services, X Window, Printing Services, Desktop Services, Sound Services,
> LDAP, Certificate Services]: Structure section by adding headings for each
> service (in a broader snse fo service), ensure @anchors exist for each
> heading and create a @menu at the top of the section.
I’m less convinced about this one. I wonder if, instead of adding
anchors, we should add proper sectioning at the same level as the
existing sections (“Base Services”, etc.).
Also, I don’t think we need one section (or anchor) per service:
mingetty, agetty, and kmscon typically belong in the same section;
likewise for urandom and rngd; udev, syslog, and nscd are arguably good
fits under “Base Services”.
WDYT?
> +* Services related to files::
> +* Hostname::
Typographic note: titles should be capitalized, and “host name” is two
words. :-)
IWBN to have synopses after double colons like you did in the first
patch.
Ludo’.
next prev parent reply other threads:[~2022-07-03 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 14:45 [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Hartmut Goebel
2022-06-22 15:55 ` [bug#56145] [PATCH 1/5] doc: Add menus to Services sub-sections (part 1/2) Hartmut Goebel
2022-07-03 10:33 ` [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Ludovic Courtès
2022-06-22 15:55 ` [bug#56145] [PATCH 2/5] doc: Add menus to Services sub-sections (part 2/2) Hartmut Goebel
2022-07-03 10:38 ` Ludovic Courtès [this message]
2022-07-04 14:30 ` [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Hartmut Goebel
2022-07-04 20:08 ` Ludovic Courtès
2022-06-22 15:55 ` [bug#56145] [PATCH 3/5] doc: Fix a URL Hartmut Goebel
2022-06-22 15:55 ` [bug#56145] [PATCH 4/5] doc: Small rewording Hartmut Goebel
2022-06-22 15:55 ` [bug#56145] [PATCH 5/5] doc: Add a URL link Hartmut Goebel
2022-06-22 18:59 ` [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jzy1nx3.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=56145@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.