unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Philip Kaludercic <philipk@posteo.net>,
	"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 18:36:53 +0200	[thread overview]
Message-ID: <CADwFkm=iSRr46CD9QLMXwCviLanFkMuV-8waNkU5fmCwcZzbJw@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB548882F377E0470D40B54168F34F9@SJ0PR10MB5488.namprd10.prod.outlook.com>

> > AFAIU, "deprecated" doesn't always imply removal,
> > whereas "obsolete" does.
>
> No, it doesn't.
>
> Even desupporting ("unsupported") doesn't [...]

We don't use the term "desupporting" in Emacs, AFAIK.

Look, I'm merely trying to describe how we currently seem to be using
these terms in the Emacs project.  I might be wrong, of course, in
which case I trust that our maintainers will make the necessary
corrections.

Naturally, we are all entitled to our personal opinions about how we'd
like to see these terms used in an ideal world.  That's fine and, as
you note, different organizations use them differently.  However, I
don't think discussing that here will necessarily lead to more clarity
about our current and past usage of these terms.  I would therefore
suggest starting a new thread if there is a need for such a discussion
(e.g., if you are not happy with how they are currently used).

That said, the above could have been more clear if I said "eventual"
or "future" removal instead.  That point is taken.



  reply	other threads:[~2022-09-21 16:36 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               ` [External] : " Drew Adams
2022-09-21 16:36                 ` Stefan Kangas [this message]
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

  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='CADwFkm=iSRr46CD9QLMXwCviLanFkMuV-8waNkU5fmCwcZzbJw@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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).