From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Please rename trusted-content to trusted-contents
Date: Fri, 20 Dec 2024 14:30:14 +0200 [thread overview]
Message-ID: <86ikrea65l.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmZpsw3TmxbS1YiY5dpb-Hj0yTR7JwY1Z5PaxLu1iAC1Q@mail.gmail.com> (message from Stefan Kangas on Fri, 20 Dec 2024 04:42:31 -0500)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Fri, 20 Dec 2024 04:42:31 -0500
> Cc: emacs-devel@gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Richard Stallman <rms@gnu.org>
> >> Date: Fri, 20 Dec 2024 00:23:32 -0500
> >>
> >> "Contents" and "content" are two different words, and for this
> >> meaning, "contents" is correct. It means the contents of the
> >> file, and that's what we refer to here.
> >>
> >> Please let's rename that symbol now before it gets into a release.
> >
> > The Emacs 30.0.93 pretest was already uploaded with "trusted-content"
> > in it. So if we rename it now, we will need to support both
> > spellings, via defvaralias. I'm not sure the problem is acute enough
> > to justify such last-minute changes.
>
> Do we really maintain backwards-compatibility with all pretest releases
> also? I usually consider them more like development branches: used for
> testing, not for production.
We don't usually maintain compatibility in those cases, but this
situation is special: we are very close to the release, and I don't
want to waste one more pretest because we renamed the variable.
> In any case, I think using the right word is better, so if we need a
> defvaralias then so be it, IMO. I don't see how it could hurt, and we
> could even define-obsolete-variable-alias.
From where I stand, if we decide to rename it, we must have a
defvaralias for the other name.
And FWIW, renaming doesn't sound very important to me: Emacs is full
of mis-spellings and English usage that is not 110% correct, so I
don't see this as a catastrophe. After all, Stefan's English is
either his first language or close, so if he is okay with that name,
we are not in a bad place.
prev parent reply other threads:[~2024-12-20 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 5:23 Please rename trusted-content to trusted-contents Richard Stallman
2024-12-20 7:52 ` Eli Zaretskii
2024-12-20 9:42 ` Stefan Kangas
2024-12-20 12:30 ` Eli Zaretskii [this message]
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ikrea65l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
/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/emacs.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).