From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Backend is not a word
Date: Mon, 17 Sep 2001 17:17:42 -0400 [thread overview]
Message-ID: <2n3d5lldop.fsf@piglet.jia.vnet> (raw)
[-- Attachment #1: Type: text/plain, Size: 142 bytes --]
"Backend" is not a word. RMS suggests to use "back end", while
"back-end" is found in FOLDOC. What should we write? Opinions?
ShengHuo
[-- Attachment #2: Type: message/rfc822, Size: 550 bytes --]
From: Richard Stallman <rms@gnu.org>
To: gerd@gnu.org
Subject: Pain in the backend
Date: Thu, 13 Sep 2001 07:57:35 -0600 (MDT)
Message-ID: <200109131357.HAA10072@aztec.santafe.edu>
Could you ask the person who maintains gnus.texi to write "back end"
as two words, not as one word "backend"?
next reply other threads:[~2001-09-17 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 21:17 ShengHuo ZHU [this message]
2001-09-17 21:34 ` Paul Jarc
2001-09-17 22:30 ` Russ Allbery
2001-09-22 22:06 ` Gaute B Strokkenes
2001-09-18 7:57 ` Mats Lidell
2001-09-17 22:28 ` Wes Hardaker
2001-09-18 7:41 ` Didier Verna
2001-09-18 12:50 ` Per Abrahamsen
2001-12-30 3:25 ` Lars Magne Ingebrigtsen
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=2n3d5lldop.fsf@piglet.jia.vnet \
--to=zsh@cs.rochester.edu \
/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.
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 NNTP newsgroup(s).