unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alexis <flexibeast@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Magit obsolete ?
Date: Fri, 08 Feb 2019 12:14:34 +1100	[thread overview]
Message-ID: <875ztv13ph.fsf@ada> (raw)
In-Reply-To: <20190207172223.21fc232f@mistral>


jonetsu <jonetsu@teksavvy.com> writes:

> Hello,  
>
> I'm looking for git support within emacs.  After browsing here 
> and
> there it looks like Magit would be a good contender.  The latest 
> update
> on the Magit web page is from the end of last year.  The version 
> in
> melpa seems even more recent: 20190202.1535.
>
> However the first two description lines of the package in melpa 
> are:
>
> magit is an available obsolete package.
>
> Status: Available Obsolete from melpa
>
> What gives ?

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".


Alexis.



  parent reply	other threads:[~2019-02-08  1:14 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 [this message]
2019-02-08 14:37   ` jonetsu
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=875ztv13ph.fsf@ada \
    --to=flexibeast@gmail.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).