unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Richard Stallman <rms@gnu.org>
Cc: dick.r.chiang@gmail.com,  emacs-devel@gnu.org
Subject: Re: NonGNU or Commercial Emacs
Date: Sun, 12 Sep 2021 17:37:36 +0800	[thread overview]
Message-ID: <87czpekucf.fsf@yahoo.com> (raw)
In-Reply-To: <E1mPEaI-0002a1-In@fencepost.gnu.org> (Richard Stallman's message of "Sat, 11 Sep 2021 21:47:06 -0400")

Richard Stallman <rms@gnu.org> writes:

> Would you please show me the actual text which strikes you as "extorsion"
> or "trying to extract compromises"?  If it is text in some other part of
> that site, I'd like to see it and think about it.

From the README file on that page (which requires JavaScript to be
displayed, I think):

> Isn't this xemacs all over again?
> Ah, but if it could reach those heights. If by some miracle it did, the
> choices for the FSF are the same as before: enlist RMS to embark on a
> coding frenzy that achieves feature parity, grant myself commit rights,
> or continue not noticing me. If my history of user acquisition is any
> indication, the last outcome is most likely.

Perhaps I chose the word 'extorsion' poorly, but if so could anyone tell
me a better word for "demanding commit rights"?  I think my grasp of the
English language is not always as good as I think it is.

Thanks.



  reply	other threads:[~2021-09-12  9:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 13:25 NonGNU or Commercial Emacs (was: Gitlab Migration) dick
2021-09-09 16:46 ` NonGNU or Commercial Emacs Kévin Le Gouguec
2021-09-10  1:04 ` Po Lu
2021-09-10  1:14   ` Jean-Christophe Helary
2021-09-12  1:47     ` Richard Stallman
2021-09-12  1:47   ` Richard Stallman
2021-09-12  9:37     ` Po Lu [this message]
2021-09-12 11:08       ` Arthur Miller

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=87czpekucf.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=dick.r.chiang@gmail.com \
    --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).