From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r116379: Replace "Maintainer: FSF" with the emacs-devel mailing address
Date: Tue, 11 Feb 2014 14:11:18 -0500 [thread overview]
Message-ID: <E1WDIjm-00030w-6J@fencepost.gnu.org> (raw)
In-Reply-To: <874n467rz4.fsf@lifelogs.com> (message from Ted Zlatanov on Mon, 10 Feb 2014 13:17:03 -0500)
[[[ 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. ]]]
maintainer-wanted@gnu.org (redirecting to emacs-devel perhaps) would
probably communicate most clearly.
A blanket change of this sort would be mistaken.
There are some files for which we might wish to find a specific
maintainer. But not all of them!
For most of them, all we want to say is "no specific maintainer".
While "FSF" is not perfectly clear, it gets the point across.
"Emacs developers" would be slightly more correct, but the change
would be a lot more trouble than it is worth.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
next prev parent reply other threads:[~2014-02-11 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WCfma-0005gV-3S@vcs.savannah.gnu.org>
2014-02-10 17:05 ` [Emacs-diffs] trunk r116379: Replace "Maintainer: FSF" with the emacs-devel mailing address Stefan Monnier
2014-02-10 17:12 ` Glenn Morris
2014-02-10 18:17 ` Ted Zlatanov
2014-02-10 18:20 ` Glenn Morris
2014-02-11 19:11 ` Richard Stallman [this message]
2014-02-10 19:08 ` Stefan Monnier
2014-02-10 19:23 ` Glenn Morris
2014-02-10 19:31 ` Eli Zaretskii
2014-02-10 23:13 ` Bastien
2014-02-10 23:38 ` Glenn Morris
2014-02-11 19:04 ` Achim Gratz
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=E1WDIjm-00030w-6J@fencepost.gnu.org \
--to=rms@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.