unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 42401@debbugs.gnu.org
Subject: bug#42401: 28.0.50; gnus-slave renamed to gnus-child
Date: Fri, 17 Jul 2020 08:26:40 +0800	[thread overview]
Message-ID: <87y2nj7zr3.fsf@yahoo.com> (raw)
In-Reply-To: 87y2nj7zr3.fsf.ref@yahoo.com


For some reason, gnus-slave has been renamed to gnus-child without
appropriate aliases.  Reacting to the latest ridiculousness occuring in
society is already stupid, but breaking backwards compatibility for them
is even worse.  The term `slave' used in the `gnus-slave' sense has no
connotations towards racism or slavery.  Similarly, the term
`gnus-child' has no connotations towards adult-ism or child
'oppression', if we ever get to that.  Instead of changing things at
random, why don't we just stick with one name that works?  I doubt it's
possible to find any term that doesn't become offensive at one point.

(P.S: I'm asian and I find the face `term-color-yellow' offensive /s)


In GNU Emacs 28.0.50 (build 466, x86_64-pc-linux-gnu, GTK+ Version 3.98.5, cairo version 1.17.3)
 of 2020-07-14 built on local-build-system
Repository revision: a3f4f737ce2d31b143586ded6697e910248dfb87
Repository branch: mashup
Windowing system distributor 'The GNU project's GTK toolkit.', version 3.98.5
System Description: Fedora 32 (Workstation Edition)





       reply	other threads:[~2020-07-17  0:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y2nj7zr3.fsf.ref@yahoo.com>
2020-07-17  0:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-07-17  1:06   ` bug#42401: 28.0.50; gnus-slave renamed to gnus-child Lars Ingebrigtsen
2020-07-17  2:00     ` Lars Ingebrigtsen
2020-07-17  7:55       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-17 12:57         ` Lars 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

  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=87y2nj7zr3.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=42401@debbugs.gnu.org \
    --cc=luangruo@yahoo.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).