From: Eli Zaretskii <eliz@gnu.org>
To: Alex Bochannek <alex@bochannek.com>
Cc: larsi@gnus.org, 48801@debbugs.gnu.org
Subject: bug#48801: 28.0.50; [PATCH] Feature suggestion gnus-retrieve-headers check for nov-is-evil when agent is enabled
Date: Wed, 09 Jun 2021 21:55:25 +0300 [thread overview]
Message-ID: <83o8cedg0y.fsf@gnu.org> (raw)
In-Reply-To: <m2zgvy7u4b.fsf@bochannek.com> (message from Alex Bochannek on Wed, 09 Jun 2021 11:47:32 -0700)
> From: Alex Bochannek <alex@bochannek.com>
> Cc: larsi@gnus.org, 48801@debbugs.gnu.org
> Date: Wed, 09 Jun 2021 11:47:32 -0700
>
> > Our conventions are to leave 2 spaces between sentences.
>
> Thanks for pointing that out! Is there a style document for code and
> documentation that I could use as a reference?
We use US English conventions, both for spelling and for punctuation.
I don't think we spell out these conventions explicitly somewhere, not
in their entirety anyway. However, CONTRIBUTE does mention this
particular rule.
next prev parent reply other threads:[~2021-06-09 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 21:13 bug#48801: 28.0.50; [PATCH] Feature suggestion gnus-retrieve-headers check for nov-is-evil when agent is enabled Alex Bochannek
2021-06-03 7:59 ` Lars Ingebrigtsen
2021-06-03 18:01 ` Alex Bochannek
2021-06-04 9:35 ` Lars Ingebrigtsen
2021-06-04 17:40 ` Alex Bochannek
2021-06-06 9:36 ` Lars Ingebrigtsen
2021-06-06 17:51 ` Alex Bochannek
2021-06-08 9:57 ` Lars Ingebrigtsen
2021-06-08 15:50 ` Alex Bochannek
2021-06-09 5:35 ` Alex Bochannek
2021-06-09 9:59 ` Lars Ingebrigtsen
2021-06-09 18:05 ` Alex Bochannek
2021-06-09 18:14 ` Eli Zaretskii
2021-06-09 18:47 ` Alex Bochannek
2021-06-09 18:55 ` Eli Zaretskii [this message]
2021-06-09 19:04 ` Alex Bochannek
2021-06-12 12:10 ` Lars Ingebrigtsen
2021-06-12 17:49 ` Alex Bochannek
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=83o8cedg0y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48801@debbugs.gnu.org \
--cc=alex@bochannek.com \
--cc=larsi@gnus.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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.