unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean-Christophe Helary <brandelune@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, Richard Stallman <rms@gnu.org>
Subject: Re: Robert J. Chassel reference in Intro to Emacs Lisp
Date: Sun, 19 May 2019 10:55:53 +0900	[thread overview]
Message-ID: <96FD9F4C-2D41-4BF7-94C6-BEB4CEED2694@gmail.com> (raw)
In-Reply-To: <E1hS74f-0005a9-Tv@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 331 bytes --]


> On May 19, 2019, at 6:41, Richard Stallman <rms@gnu.org> wrote:
> 
> Aside from that, please change "passed away" to "died".
> As a founding member of the anti-euphemism league, I must insist.

Here it is.

Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune



[-- Attachment #2.1: Type: text/html, Size: 1841 bytes --]

[-- Attachment #2.2: 0001-Bob-Chassel-died.patch --]
[-- Type: application/octet-stream, Size: 971 bytes --]

From 6995cd87956ed952fee32973fdeb72e1f925fbeb Mon Sep 17 00:00:00 2001
From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Date: Sun, 19 May 2019 10:52:08 +0900
Subject: [PATCH] Bob Chassel *died*

---
 doc/lispintro/emacs-lisp-intro.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index 09b6698722..af12e1e7c8 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -21865,7 +21865,7 @@ About the Author
 the @cite{Texinfo} manual, and edited more than a dozen other
 books.  He graduated from Cambridge University, in England.  He had an
 abiding interest in social and economic history and flew his own
-airplane.  He passed away on 30 June 2017.
+airplane.  He died on 30 June 2017.
 
 @uref{https://www.fsf.org/blogs/community/goodbye-to-bob-chassell,
 "Goodbye to Bob Chassell"}
-- 
2.21.0


[-- Attachment #2.3: Type: text/html, Size: 206 bytes --]

  reply	other threads:[~2019-05-19  1:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18 12:42 Robert J. Chassel reference in Intro to Emacs Lisp Jean-Christophe Helary
2019-05-18 13:15 ` Richard Copley
2019-05-18 14:03   ` Jean-Christophe Helary
2019-05-18 14:31     ` Jean-Christophe Helary
2019-05-18 18:08       ` Paul Eggert
2019-05-18 21:41         ` Richard Stallman
2019-05-19  1:55           ` Jean-Christophe Helary [this message]
2019-05-19 16:32           ` Omitting "Maintainer:" (was: Robert J. Chasell reference ...) Paul Eggert
2019-05-19 16:44             ` Omitting "Maintainer:" Stefan Monnier
2019-05-19 17:02               ` Eli Zaretskii
2019-05-19 19:18             ` Lars Ingebrigtsen
2019-05-20  4:38               ` Paul Eggert
2019-05-19 20:47             ` Omitting "Maintainer:" (was: Robert J. Chasell reference ...) 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

  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=96FD9F4C-2D41-4BF7-94C6-BEB4CEED2694@gmail.com \
    --to=brandelune@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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.
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).