From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Does Richard M. Stallman still scrutinize and develop the codes of Emacs now?
Date: Sun, 15 Aug 2021 15:35:37 +0800 [thread overview]
Message-ID: <CAGP6POLSp_m-d-7eRnagxMkn1bqDDV1CM6Sd8kzLWuF6qwDtMw@mail.gmail.com> (raw)
In-Reply-To: <83sfzb9nx8.fsf@gnu.org>
On Sun, Aug 15, 2021 at 3:18 PM Eli Zaretskii <eliz@gnu.org> wrote:
> [...]
> The AUTHORS file lists contributions to Emacs since the very
> beginning, more than 35 years ago. Any contributions since then till
> this day are reflected in AUTHORS, and what the contributors do lately
> doesn't matter at all. How far back did you go in your study of RMS's
> contributions?
I got some clues based on some digging into the Emacs git repo, as shown below:
$ git log -1
commit 3572613550f5d1d0b3392dbc809b32f3989e2981 (HEAD -> master,
origin/master, origin/HEAD)
Author: Wolfgang Scherer <wolfgang.scherer@gmx.de>
Date: Sun Aug 15 04:02:23 2021 +0300
$ git log | grep -m1 -A1 -B1 -i 'Richard M. Stallman'
commit dca743f0941909a80e3f28c023977120b6203e20
Author: Richard M. Stallman <rms@gnu.org>
Date: Sun Mar 22 03:51:55 2015 -0400
The most recent commit by RMS was done in 2015.
Best, Hongyi
next prev parent reply other threads:[~2021-08-15 7:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 6:46 Does Richard M. Stallman still scrutinize and develop the codes of Emacs now? Hongyi Zhao
2021-08-15 6:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 7:02 ` Jean-Christophe Helary
2021-08-15 7:15 ` Hongyi Zhao
2021-08-15 7:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 7:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 7:17 ` Eli Zaretskii
2021-08-15 7:35 ` Hongyi Zhao [this message]
2021-08-15 7:42 ` Hongyi Zhao
2021-08-15 8:08 ` Eli Zaretskii
2021-08-15 8:22 ` Hongyi Zhao
2021-08-15 8:29 ` Stephen Berman
2021-08-15 8:41 ` Hongyi Zhao
2021-08-15 9:28 ` Teemu Likonen
2021-08-15 11:54 ` Hongyi Zhao
2021-08-15 12:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 13:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-21 22:05 ` Wayne Harris via Users list for the GNU Emacs text editor
2021-08-22 0:53 ` Jude DaShiell
2021-08-22 1:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 1:14 ` Jude DaShiell
2021-08-22 1:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 7:03 ` tomas
2021-08-22 7:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 17:05 ` Samuel Banya
2021-08-22 17:17 ` Eli Zaretskii
2021-08-22 17:49 ` Arthur Miller
2021-08-22 19:15 ` Samuel Banya
2021-08-23 18:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-23 21:01 ` Tim Johnson
2021-08-25 9:04 ` Jean Louis
2021-08-25 22:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-22 13:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 10:08 ` Arthur Miller
2021-08-19 6:13 ` Jean Louis
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=CAGP6POLSp_m-d-7eRnagxMkn1bqDDV1CM6Sd8kzLWuF6qwDtMw@mail.gmail.com \
--to=hongyi.zhao@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).