From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: stefan@marxist.se, 46472@debbugs.gnu.org
Subject: bug#46472: Make lisp/mail/uce.el obsolete
Date: Thu, 04 Mar 2021 05:39:06 +0200 [thread overview]
Message-ID: <83czwfk2p1.fsf@gnu.org> (raw)
In-Reply-To: <jwvh7lsorwg.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 03 Mar 2021 16:22:16 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Stefan Kangas <stefan@marxist.se>, 46472@debbugs.gnu.org
> Date: Wed, 03 Mar 2021 16:22:16 -0500
>
> > What are the reasons for moving uce.el to obsolete/ ?
>
> I don't think it's useful to anyone.
> Moving it to `obsolete` might let us discover that I'm wrong on this
> point, of course ;-)
I'm against this method of "discovery", sorry. This package doesn't
require any maintenance, so let's not invent any maintenance for it.
We have more important things to do with our time (I hope).
prev parent reply other threads:[~2021-03-04 3:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 21:58 bug#46472: Make lisp/mail/uce.el obsolete Stefan Kangas
2021-02-13 7:58 ` Eli Zaretskii
2021-02-13 12:25 ` Stefan Kangas
2021-02-13 14:00 ` Eli Zaretskii
2021-03-04 19:27 ` Glenn Morris
2021-03-04 21:12 ` Eli Zaretskii
2021-03-06 17:14 ` Stefan Kangas
2021-03-06 17:25 ` Eli Zaretskii
2022-06-17 13:07 ` Lars Ingebrigtsen
2021-10-12 4:33 ` Stefan Kangas
2021-10-12 13:52 ` Eli Zaretskii
2021-10-12 16:12 ` Stefan Kangas
2021-10-12 16:44 ` Eli Zaretskii
2021-10-12 17:29 ` Stefan Kangas
2021-10-12 18:50 ` Eli Zaretskii
2021-10-14 20:45 ` Stefan Kangas
2021-10-15 6:12 ` Eli Zaretskii
2021-10-15 8:50 ` Stefan Kangas
2021-10-15 10:46 ` Eli Zaretskii
2021-10-16 12:48 ` Stefan Kangas
2021-10-16 12:50 ` Eli Zaretskii
2021-10-17 23:56 ` Stefan Kangas
2021-10-16 12:32 ` Stefan Kangas
2021-03-03 21:22 ` Stefan Monnier
2021-03-04 3:39 ` Eli Zaretskii [this message]
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=83czwfk2p1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46472@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.