From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org, lxsameer@gnu.org
Subject: Re: How much I can rely on etc/TODO
Date: Wed, 10 Apr 2019 18:48:54 +0300 [thread overview]
Message-ID: <83tvf56eu1.fsf@gnu.org> (raw)
In-Reply-To: <E1hDzvp-0000w3-NZ@fencepost.gnu.org> (message from Richard Stallman on Tue, 09 Apr 2019 19:13:33 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: lxsameer@gnu.org, emacs-devel@gnu.org
> Date: Tue, 09 Apr 2019 19:13:33 -0400
>
> > The last non-trivial change was a year ago. The one before that, 2
> > years ago.
>
> It sounds like we're updating the file just fine,
> but we're not doing much works on the tasks listed in it.
Was it ever different? If it was, I don't remember.
> We're adding a lot of features to Emacs, but not based on plans.
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;
telling them something else is much more important for Emacs is
unlikely to change their preferences.
next prev parent reply other threads:[~2019-04-10 15:48 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 [this message]
2019-04-10 21:53 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tvf56eu1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lxsameer@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 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.