From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Pertinent NEWS parts for the Emacs 26 manual draft
Date: Sat, 30 Sep 2017 19:14:40 -0400 [thread overview]
Message-ID: <E1dyQy0-0004Bk-7z@fencepost.gnu.org> (raw)
In-Reply-To: <83377465en.fsf@gnu.org> (message from Eli Zaretskii on Sat, 30 Sep 2017 09:56:32 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Since I've already asked Nicolas to make a pretest for Emacs 26.1, it
> should be clear that NEWS was already reviewed (by me in this case),
> and any such blunders, if there were ones, were already fixed.
I'm glad this is so. I didn't know how things stood.
However, my main point is the last one: regardless of the current state
of marking up NEWS, we still need someone to collect just the parts
that checkers should read.
> NEWS has separate sections for Lisp and non-Lisp changes.
To make things really easy, we should omit the parts of NEWS that
aren't pertinent and someone doesn't need to read for this purpose.
Would someone please volunteer to do it?
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
next prev parent reply other threads:[~2017-09-30 23:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 22:08 Pertinent NEWS parts for the Emacs 26 manual draft Richard Stallman
2017-09-29 10:07 ` Eli Zaretskii
2017-09-29 21:55 ` Richard Stallman
2017-09-30 6:56 ` Eli Zaretskii
2017-09-30 23:14 ` Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-09 18:16 Richard Stallman
2017-09-21 18:26 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1dyQy0-0004Bk-7z@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.