From: jonetsu <jonetsu@teksavvy.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Magit obsolete ?
Date: Fri, 8 Feb 2019 09:37:38 -0500 [thread overview]
Message-ID: <20190208093738.451aee60@mistral> (raw)
In-Reply-To: <875ztv13ph.fsf@ada>
On Fri, 08 Feb 2019 12:14:34 +1100
Alexis <flexibeast@gmail.com> wrote:
> Maybe i'm misunderstanding you, but in the context of ELPAs like
> MELPA, 'obsolete' often/usually means "a newer version of this
> package is available". So if version 20190202.1535 of Magit is
> available, but you were looking at the description for an earlier
> version, e.g. 20190201.2340, you'll be told that version is
> "obsolete".
>
> Of course, this is indeed a different meaning to how 'obsolete' is
> used in non-ELPA Emacs contexts, where "this library is obsolete"
> often/usually means "don't use this library any more".
It's an unfortunate choice to use this word. 'Obsolete'
carries a pronounced definitive sense to it. Amongst the synonyms are
'old-fashioned', 'antediluvian' and 'anachronistic' :)
A bit drastic for a day-old version I'd say.
Cheers.
next prev parent reply other threads:[~2019-02-08 14:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 22:22 Magit obsolete ? jonetsu
2019-02-07 23:07 ` Emanuel Berg
2019-02-07 23:12 ` Emanuel Berg
2019-02-08 0:19 ` Drew Adams
2019-02-08 0:28 ` Emanuel Berg
2019-02-08 1:01 ` Drew Adams
2019-02-08 14:51 ` Emanuel Berg
2019-02-07 23:33 ` Amin Bandali
2019-02-08 1:17 ` Brett Gilio
2019-02-08 14:58 ` Emanuel Berg
2019-02-08 0:25 ` jonetsu
2019-02-08 0:38 ` Emanuel Berg
2019-02-08 0:50 ` jonetsu
2019-02-08 1:14 ` Alexis
2019-02-08 14:37 ` jonetsu [this message]
2019-02-08 14:57 ` Emanuel Berg
2019-02-08 15:18 ` jonetsu
2019-02-08 15:23 ` Emanuel Berg
2019-02-08 15:40 ` jonetsu
2019-02-08 15:03 ` Stefan Monnier
2019-02-08 15:52 ` jonetsu
2019-02-08 16:51 ` Phillip Lord
2019-02-08 17:15 ` Brett Gilio
2019-02-08 18:14 ` Emanuel Berg
2019-02-08 18:16 ` A540OJhQ3kS
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=20190208093738.451aee60@mistral \
--to=jonetsu@teksavvy.com \
--cc=help-gnu-emacs@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.
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).