From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: luangruo@yahoo.com, 50999@debbugs.gnu.org, larsi@gnus.org,
stefan@marxist.se, rms@gnu.org
Subject: bug#50999: [External] : bug#50999: 29.0.50; Deleting libraries obsolete since Emacs 24
Date: Sun, 14 Nov 2021 20:57:38 +0200 [thread overview]
Message-ID: <83ee7itvj1.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB548871937E0118E2B7379276F3979@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sun, 14 Nov 2021 18:35:06 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "larsi@gnus.org" <larsi@gnus.org>,
> "luangruo@yahoo.com"
> <luangruo@yahoo.com>,
> "50999@debbugs.gnu.org" <50999@debbugs.gnu.org>,
> "stefan@marxist.se" <stefan@marxist.se>, "rms@gnu.org" <rms@gnu.org>
> Date: Sun, 14 Nov 2021 18:35:06 +0000
> Accept-Language: en-US
>
> > > The point is that there's no obligation to make
> > > changes (maintenance or other) to code that you've
> > > declared is "obsolete".
> >
> > It's easy for you to say that, since you don't have to pick up the
> > gauntlet of the maintenance. The downside is non-negligible.
>
> What's the obligation to maintain any particular
> obsolete code?
Lars answered that up-thread.
next prev parent reply other threads:[~2021-11-14 18:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 21:42 bug#50999: 29.0.50; Deleting libraries obsolete since Emacs 24 Stefan Kangas
2021-10-04 9:40 ` Lars Ingebrigtsen
2021-10-04 13:25 ` Stefan Kangas
2021-10-05 7:02 ` Lars Ingebrigtsen
2021-10-05 12:27 ` Eli Zaretskii
2021-10-05 13:07 ` Phil Sainty
2021-10-05 13:39 ` Stefan Kangas
2021-10-06 1:28 ` Phil Sainty
2021-10-05 13:39 ` Stefan Kangas
2021-12-03 14:56 ` Stefan Kangas
2021-12-03 16:47 ` bug#50999: [External] : " Drew Adams
2021-12-07 21:26 ` Stefan Kangas
2021-12-07 21:34 ` Drew Adams
2021-12-07 21:58 ` Stefan Kangas
2021-12-04 1:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-05 12:31 ` Stefan Kangas
2021-12-05 12:31 ` Stefan Kangas
2021-12-05 20:55 ` Glenn Morris
2021-12-07 2:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-07 3:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-08 1:37 ` Stefan Kangas
2021-12-08 2:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-04 9:22 ` Eli Zaretskii
2021-12-04 10:32 ` Stefan Kangas
2022-06-17 12:03 ` Stefan Kangas
2021-11-10 11:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-12 4:20 ` Richard Stallman
2021-11-12 4:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-12 4:59 ` Lars Ingebrigtsen
2021-11-12 5:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-12 6:27 ` Lars Ingebrigtsen
2021-11-12 6:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-14 0:47 ` Lars Ingebrigtsen
2021-11-14 17:48 ` bug#50999: [External] : " Drew Adams
2021-11-14 17:53 ` Eli Zaretskii
2021-11-14 18:04 ` Drew Adams
2021-11-14 18:18 ` Eli Zaretskii
2021-11-14 18:35 ` Drew Adams
2021-11-14 18:57 ` Eli Zaretskii [this message]
2021-11-14 21:33 ` Drew Adams
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=83ee7itvj1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50999@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=rms@gnu.org \
--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 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).