unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lxsameer@gnu.org, emacs-devel@gnu.org
Subject: Re: How much I can rely on etc/TODO
Date: Wed, 10 Apr 2019 17:53:03 -0400	[thread overview]
Message-ID: <E1hEL9T-0003Po-IF@fencepost.gnu.org> (raw)
In-Reply-To: <83tvf56eu1.fsf@gnu.org> (message from Eli Zaretskii on Wed, 10 Apr 2019 18:48:54 +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. ]]]

  > I don't remember Emacs development ever advancing according to plan.
  > It would be nice to have that, I agree, but I don't think it's
  > possible in practice.  People work on what they feel like working;

That's the attitude that Emacs developers have now.  But it is not
inevitable.  Let's try to lead and inspire people to work on some
things that would be a big advance.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2019-04-10 21:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 17:52 How much I can rely on etc/TODO Sameer Rahmani
2019-04-08 17:59 ` Eli Zaretskii
2019-04-08 18:26   ` Sameer Rahmani
2019-04-08 20:42     ` Basil L. Contovounesios
2019-04-08 22:14   ` Richard Stallman
2019-04-09  6:03     ` Eli Zaretskii
2019-04-09  7:50       ` lxsameer
2019-04-09  9:39         ` Eli Zaretskii
2019-04-09 12:05           ` Sergey Organov
2019-04-09 13:52         ` Drew Adams
2019-04-09 23:13       ` Richard Stallman
2019-04-10 15:48         ` Eli Zaretskii
2019-04-10 21:53           ` Richard Stallman [this message]
2019-04-11 14:12             ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2019-04-11  1:34 Van L

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=E1hEL9T-0003Po-IF@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lxsameer@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).