From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31597@debbugs.gnu.org, eller.helmut@gmail.com
Subject: bug#31597: 27.0.50; Annoying ' to ’ translation
Date: Sun, 27 May 2018 19:33:53 +0000 [thread overview]
Message-ID: <20180527193353.GB11447@ACM> (raw)
In-Reply-To: <831sdx806a.fsf@gnu.org>
Hello, Eli.
On Sun, May 27, 2018 at 20:42:53 +0300, Eli Zaretskii wrote:
> > Date: Sun, 27 May 2018 17:12:17 +0000
> > Cc: eller.helmut@gmail.com, 31597@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> > > > The person behind the change, Paul Eggert, simply pushed it through
> > > > without first securing agreement from Emacs as a whole, and had the
> > > > political skills to prevent a consensus on the matter prevailing.
> > > This misrepresents what Paul did and say, and I think is grossly
> > > unfair to him.
> > This was a highly controversial change. Paul could first have committed
> > the changes on a branch and invited comment.
> Saying this is a far cry from accusing Paul in nasty political tricks
> and in deliberately sneaking controversial code behind our backs.
He sneaked in this code in front of our noses, but none of us really
appreciated what was going on. I certainly didn't (until later).
> > You weren't really involved in the fight against this. I was, and it
> > exhausted me.
> I hear you, and you should know very well that I'm not too
> enthusiastic about this change, either. But we should be able to
> disagree without name-calling.
It was me that rolled with the punches. Soon after this thing started, I
committed an "emergency" user option to allow people to disable this
forced character substitution. Within hours, this option had been
"polluted" so as not quite to work. And shortly before Emacs 25 was
released, the option was quietly degraded to a non-option variable, which
one of the manuals said was for "advanced use" only. This is the sort of
manoevering I was up against. (The option is now back in Emacs 26.)
> > > I wish we avoided such ad-hominem attacks, just because we disagree.
> > Eli, my view of things is NOT an ad-hominem. An ad-hominem is when one
> > argues by attacking a _person_. My paragraph above does not do this: it
> > criticizes Paul's _actions_. I think it is a fair summary of what
> > actually happened.
> The wording you've chosen to do that is what I hope we could avoid.
OK. But I don't think it's healthy to pretend that the above didn't
happen, and that everybody is kind, considerate, and respectful to
everybody else all the time. I don't think either of us want anything
like this to happen again. I would hope that, in future, all
controversial changes get argued out first, and if committed to the
repository, they go on a branch first.
And the OP, Helmut Eller, deserves an explanation of how the current
state of affairs, which he has reported as a bug, came about.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-05-27 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 20:46 bug#31597: 27.0.50; Annoying ' to ’ translation Helmut Eller
2018-05-25 21:31 ` Tomas Nordin
2018-05-25 21:33 ` Tomas Nordin
[not found] ` <mailman.494.1527281229.1292.bug-gnu-emacs@gnu.org>
2018-05-27 9:32 ` Alan Mackenzie
2018-05-27 16:04 ` Eli Zaretskii
2018-05-27 17:12 ` Alan Mackenzie
2018-05-27 17:42 ` Eli Zaretskii
2018-05-27 19:33 ` Alan Mackenzie [this message]
2018-05-27 22:23 ` Noam Postavsky
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=20180527193353.GB11447@ACM \
--to=acm@muc.de \
--cc=31597@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@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).