From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: mirai <mirai@makinata.eu>
Cc: 59700@debbugs.gnu.org
Subject: [bug#59700] [DOCUMENTATION] [PATCH] doc: Move %facebook-host-aliases to operating-system.
Date: Thu, 05 Jan 2023 11:23:05 -0500 [thread overview]
Message-ID: <87y1qhne6u.fsf@gmail.com> (raw)
In-Reply-To: <8319843d-abb5-afdb-e828-8faaf33ad593@makinata.eu> (mirai@makinata.eu's message of "Thu, 5 Jan 2023 16:07:01 +0000")
Hi,
mirai <mirai@makinata.eu> writes:
> On 2023-01-03 22:01, Maxim Cournoyer wrote:
>> Moving %facebook-hosts-aliases to under the 'operating-system Reference'
>> from network services doesn't seem an improvement to me (it seems even
>> more out of place to me).
>
> I placed it under 'operating-system Reference' because of the proximity to 'hosts-file' field
> and the usage example seems to suggest it's a better fit here.
>
>>
>> I'd err on the side of the status quo.
>>
>> What do you think?
>
> I think its current location (Network services) is extremely strange as %facebook-host-aliases
> is not a service and given the usage example it fits better elsewhere.
I gathered another opinion on #guix from civodul, which thought status
quo is appropriate, though they mentioned turning host-file into a
service would be nice to make it more extendable. Perhaps you could
look into this, if you want to improve things in that direction?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-01-05 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 21:44 [bug#59700] [PATCH 0/1] doc: Move %facebook-host-aliases to operating-system Bruno Victal
2022-11-29 21:47 ` [bug#59700] [PATCH 1/1] " mirai
2023-01-03 22:01 ` [bug#59700] [DOCUMENTATION] [PATCH] " Maxim Cournoyer
2023-01-03 22:07 ` Ryan Sundberg via Guix-patches via
2023-01-05 16:07 ` mirai
2023-01-05 16:23 ` Maxim Cournoyer [this message]
2023-02-09 1:02 ` bug#59700: (no subject) Bruno Victal
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1qhne6u.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=59700@debbugs.gnu.org \
--cc=mirai@makinata.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).