all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 56145@debbugs.gnu.org
Subject: [bug#56145] [PATCH 0/5] Add menus to Services sub-sections
Date: Mon, 4 Jul 2022 16:30:14 +0200	[thread overview]
Message-ID: <92089bc8-c60e-aa33-b285-807d4fc7992f@crazy-compilers.com> (raw)
In-Reply-To: <874jzy1nx3.fsf_-_@gnu.org>

Am 03.07.22 um 12:38 schrieb Ludovic Courtès:

> 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.).
I don't actually understand what you mean. Currently each section 
described one or more services. The section groups the services into 
„all LDAP related‘, „all X11 related“, etc. This patch basically adds 
the anchors, whereas the other patch uses the anchors that already 
exist. So basically they result in the same.

Do you suggest to split „Base Services” into several sections? (Like 
„Console service“, “Randow data services‘, etc.)

> Also, I don’t think we need one section (or anchor) per service:

Having a TOC of all services is my actual intention. I want to have a 
list which


> 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.
I'll fix this (and the remarks on the other patch) in the next reroll, 
after we agreed on how this should look like in the end.

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |





  reply	other threads:[~2022-07-04 14:31 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   ` [bug#56145] [PATCH 0/5] Add menus to Services sub-sections Ludovic Courtès
2022-07-04 14:30     ` Hartmut Goebel [this message]
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=92089bc8-c60e-aa33-b285-807d4fc7992f@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=56145@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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.