From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefankangas@gmail.com>,
Philip Kaludercic <philipk@posteo.net>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: master d506d91b1f 2/2: Make linum.el obsolete
Date: Wed, 21 Sep 2022 16:13:31 +0000 [thread overview]
Message-ID: <SJ0PR10MB548882F377E0470D40B54168F34F9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CADwFkmn-YOeaVHU80-cBfQSDkkwEJq607pARZh4TsObnOQJM-Q@mail.gmail.com>
> AFAIU, "deprecated" doesn't always imply removal,
Yes.
> whereas "obsolete" does.
No, it doesn't.
Even desupporting ("unsupported") doesn't
require code removal. It just means that
you can't expect it to work and you can't
expect any support (help) for it.
Of course, anyone and any organization can
define any such terms the way they want.
next prev parent reply other threads:[~2022-09-21 16:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166370103866.17769.3203831255447980421@vcs2.savannah.gnu.org>
[not found] ` <20220920191039.C61BCC00874@vcs2.savannah.gnu.org>
2022-09-21 7:50 ` master d506d91b1f 2/2: Make linum.el obsolete Philip Kaludercic
2022-09-21 8:37 ` Stefan Kangas
2022-09-21 9:45 ` Philip Kaludercic
2022-09-21 12:35 ` Stefan Kangas
2022-09-21 12:43 ` Philip Kaludercic
2022-09-21 13:58 ` Stefan Kangas
2022-09-21 16:13 ` Drew Adams [this message]
2022-09-21 16:36 ` [External] : " Stefan Kangas
2022-09-21 18:26 ` Philip Kaludercic
2022-09-21 19:19 ` Stefan Kangas
2022-09-22 2:59 ` Po Lu
2022-09-22 11:01 ` Stefan Kangas
2022-09-22 11:50 ` Po Lu
2022-09-22 13:31 ` Stefan Monnier
2022-09-22 14:01 ` Stefan Kangas
2022-09-22 14:15 ` Stefan Monnier
2022-09-21 16:17 ` chad
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=SJ0PR10MB548882F377E0470D40B54168F34F9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=stefankangas@gmail.com \
/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.