From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: GNU Emacs pretest bug list <emacs-pretest-bug@gnu.org>,
GNUS mailing list <ding@gnus.org>
Subject: Re: Typo in gnus-sum?
Date: Tue, 12 Jun 2001 11:48:31 +0300 (IDT) [thread overview]
Message-ID: <Pine.SUN.3.91.1010612114811.1700L-100000@is> (raw)
In-Reply-To: <m3lmmykc2o.fsf@SnowWhite.Janik.cz>
On 11 Jun 2001, Pavel =?iso-8859-2?q?Jan=EDk?= wrote:
> Is it better? Both in 5.9.0 and current Oort.
>
> --- lisp/gnus/gnus-sum.el Thu Feb 8 01:21:04 2001
> +++ gnus-sum.el Mon Jun 11 22:12:45 2001
> @@ -819,7 +819,7 @@
>
> (defcustom gnus-ignored-from-addresses
> (and user-mail-address (regexp-quote user-mail-address))
> - "*Regexp of From headers that may be suppressed in favor of To headers."
> + "*Regexp of From headers that may be suppressed in favour of To headers."
That's the British spelling. It's up to the author(s) and
maintainer(s) of that package to decide what spelling they want to
use.
next prev parent reply other threads:[~2001-06-12 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 21:38 Pavel Janík
2001-06-12 8:48 ` Eli Zaretskii [this message]
2001-06-12 17:56 ` Richard Stallman
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=Pine.SUN.3.91.1010612114811.1700L-100000@is \
--to=eliz@is.elta.co.il \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.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.
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).