From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Idea for determining what users use
Date: 28 May 2003 02:43:24 +0200 [thread overview]
Message-ID: <5xd6i3vr2r.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200305271428.h4RES8P7007129@rum.cs.yale.edu>
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
RMS wrote:
> The first time you call it, it sends mail to
> emacs-features-used@gnu.org with subject Foo,
> asking you for permission to send it,
> and it records (setq foo t) in your .emacs file.
> If you call it again, it does nothing.
I don't really like this approach.
Rather, I agree with Stefan:
> OTOH I thought that was already the idea behing
> the `obsolete' subdirectory:
> The way I see it work, moving a package to `obsolete' is telling
> users "we think this is not used any more and we're planning to
> get rid of it. If we're wrong, you'd better tell us soon". Now
> the problem is that people might not notice that a package is obsolete.
> My recent patch for `load' to output a warning message when loading
> an `obsolete' package is a small step towards making users more
> aware of the issue.
That's a good feature IMO.
> We could go a little further, of course.
.. By telling the user that he may use "report emacs bug" to tell us
why he finds the obsoleted package useful.
In any case, I don't really see why we need to (ever) remove
anything from obsolete/ -- as long as we say that packages that
are in obsolete/ are `no longer actively supported'.
The only reason for actually removing a package from obsolete/
would be if we change basic things in emacs that causes the
package to break ... then we may choose to remove it if it is
too much work to fix.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2003-05-28 0:43 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 12:45 Idea for determining what users use Richard Stallman
2003-05-27 13:27 ` David Kastrup
2003-05-27 14:16 ` Vincent LADEUIL
2003-05-27 14:28 ` Stefan Monnier
2003-05-28 0:43 ` Kim F. Storm [this message]
2003-05-28 7:04 ` Juanma Barranquero
2003-05-28 13:54 ` Richard Stallman
2003-05-28 14:33 ` Stefan Monnier
2003-05-30 0:49 ` Richard Stallman
2003-05-27 14:39 ` Thien-Thi Nguyen
2003-05-27 15:32 ` Stephen J. Turnbull
2003-05-28 23:58 ` Richard Stallman
2003-05-29 11:35 ` Thien-Thi Nguyen
2003-05-30 0:48 ` Richard Stallman
2003-05-31 12:37 ` Thien-Thi Nguyen
2003-06-01 15:53 ` Richard Stallman
2003-06-01 20:26 ` Thien-Thi Nguyen
2003-06-03 4:06 ` Richard Stallman
[not found] ` <m1r86ktqxx.fsf@vila.local.>
2003-05-28 13:54 ` Richard Stallman
2003-05-28 14:40 ` Vincent LADEUIL
[not found] ` <m1y90rp221.fsf@vila.local.>
2003-05-30 0:49 ` Richard Stallman
2003-05-30 7:28 ` Jan D.
2003-05-30 13:29 ` Stefan Monnier
2003-05-30 14:52 ` Jan D.
2003-05-30 15:40 ` Stefan Monnier
2003-05-30 16:32 ` Alex Schroeder
2003-05-31 19:51 ` Richard Stallman
2003-06-01 0:48 ` Peter Lee
2003-06-01 1:24 ` Luc Teirlinck
2003-06-01 1:59 ` Luc Teirlinck
2003-06-02 11:16 ` Richard Stallman
2003-06-03 22:55 ` Kim F. Storm
2003-06-05 0:08 ` Richard Stallman
2003-06-06 0:21 ` Kim F. Storm
2003-06-07 10:22 ` Richard Stallman
2003-05-30 16:45 ` Jan D.
2003-05-30 16:57 ` Stefan Monnier
2003-05-31 19:51 ` Richard Stallman
2003-05-30 23:47 ` Kim F. Storm
2003-05-30 23:04 ` Miles Bader
2003-06-03 22:24 ` Kim F. Storm
2003-05-30 23:14 ` { SPAM 2 }::Re: " Luc Teirlinck
2003-05-30 23:40 ` Luc Teirlinck
2003-05-31 10:45 ` Kai Großjohann
2003-06-01 15:52 ` Richard Stallman
2003-06-01 5:06 ` Luc Teirlinck
2003-06-02 11:16 ` Richard Stallman
2003-06-03 2:43 ` Luc Teirlinck
2003-06-04 8:53 ` Richard Stallman
2003-06-03 4:05 ` Luc Teirlinck
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=5xd6i3vr2r.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--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.