From: Richard Stallman <rms@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 36478@debbugs.gnu.org
Subject: bug#36478: 26.2; Doc strings with "This function has a compiler macro..." and "This function does not change global state"
Date: Wed, 03 Jul 2019 21:35:16 -0400 [thread overview]
Message-ID: <E1hiqea-0006HP-Vj@fencepost.gnu.org> (raw)
In-Reply-To: <21500c6e-9743-40ce-89d8-d63c9351e8c0@default> (message from Drew Adams on Tue, 2 Jul 2019 13:13:40 -0700 (PDT))
[[[ 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. ]]]
> Yes, obviously; I realize that. "We" (someone)
> created and added the code that does that. And "we"
> (someone) added the descriptions of `define-inline'
> etc. to the manual. However "automatic", none of
> this fell from the sky.
I agree with your point, but that is a harsh way to put it. Would you
please make an effort to express your points in a kind way? See
https://gnu.org/philosophy/kind-communication.html.
In addition to helping people generally feel better,
it could predispose others to be more receptive to your
substantial points.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-07-04 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<13f5f7df-9017-45a0-986f-8b1a4ee0e9bd@default>
[not found] ` <<83r278cjho.fsf@gnu.org>
2019-07-02 20:13 ` bug#36478: 26.2; Doc strings with "This function has a compiler macro..." and "This function does not change global state" Drew Adams
2019-07-04 1:35 ` Richard Stallman [this message]
2019-07-02 18:05 Drew Adams
2019-07-02 19:41 ` Eli Zaretskii
2019-07-04 1:34 ` Richard Stallman
2022-02-02 18:55 ` 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=E1hiqea-0006HP-Vj@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=36478@debbugs.gnu.org \
--cc=drew.adams@oracle.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).