From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Backend is not a word
Date: 18 Sep 2001 14:50:44 +0200 [thread overview]
Message-ID: <rjadzsmzmj.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <2n3d5lldop.fsf@piglet.jia.vnet> (ShengHuo ZHU's message of "Mon, 17 Sep 2001 17:17:42 -0400")
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> "Backend" is not a word. RMS suggests to use "back end", while
> "back-end" is found in FOLDOC. What should we write? Opinions?
Use the same term as the Emacs manual. Currently, the Emacs manual
uses both "backend", "back end" and "back-end", all refering to VC
back ends. If RMS suggests using "back end", that is probably the
term he has standardized on for the Emacs manual.
next prev parent reply other threads:[~2001-09-18 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 21:17 ShengHuo ZHU
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 [this message]
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=rjadzsmzmj.fsf@ssv2.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).