From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Vagrant Cascadian <vagrant@debian.org>,
54077@debbugs.gnu.org, guix-maintainers@gnu.org
Subject: bug#54077: What does "sequel" mean in the CODE-OF-CONDUCT
Date: Sun, 27 Feb 2022 14:48:03 +0100 [thread overview]
Message-ID: <87pmn8whd8.fsf@gnu.org> (raw)
In-Reply-To: <8f4c2a2df5c805471608c4ac297a23495d9d933d.camel@telenet.be> (Maxime Devos's message of "Sun, 20 Feb 2022 21:32:51 +0100")
Hello,
Maxime Devos <maximedevos@telenet.be> skribis:
> Vagrant Cascadian schreef op zo 20-02-2022 om 12:26 [-0800]:
>> Note: In the sequel, "project" refers to GNU Guix, and "project
>> maintainer(s)" refers to maintainer(s) of GNU Guix.
>>
>> What does "the sequel" refer to?
>
> ‘The following’, I think?
Per WordNet (which is about American English):
--8<---------------cut here---------------start------------->8---
$ guix shell wordnet -- wn sequel -over
Overview of noun sequel
The noun sequel has 2 senses (no senses from tagged texts)
1. sequel, subsequence -- (something that follows something else)
2. sequel, continuation -- (a part added to a book or play that continues and extends it)
--8<---------------cut here---------------end--------------->8---
>> Maybe something more like "Note: In this document, ..." ?
If that sounds clearer, let’s do that!
Cc’ing maintainers to get their approval.
Ludo’.
next prev parent reply other threads:[~2022-02-27 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 20:26 bug#54077: What does "sequel" mean in the CODE-OF-CONDUCT Vagrant Cascadian
2022-02-20 20:32 ` Maxime Devos
2022-02-27 13:48 ` Ludovic Courtès [this message]
2022-02-27 15:50 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-02-28 1:17 ` Maxim Cournoyer
2022-03-07 8:45 ` Ludovic Courtès
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=87pmn8whd8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54077@debbugs.gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=maximedevos@telenet.be \
--cc=vagrant@debian.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 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).