From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Subject: Re: Magit obsolete ?
Date: Fri, 08 Feb 2019 01:38:35 +0100 [thread overview]
Message-ID: <86imxv5d2s.fsf@zoho.eu> (raw)
In-Reply-To: 20190207192552.6c293fea@mistral
jonetsu wrote:
>> magit is an available obsolete package.
>> Status: Available Obsolete from melpa
>
> Thanks for the replies. I found it odd that
> the melpa interface in emacs would mention
> 'obsolete'. Maybe i set up melpa wrong
> ? Hmmmm.
Here is what it says for me:
magit is an available package.
Status: Available from melpa -- [Install]
Archive: melpa
Version: 20190202.1535
Requires: emacs-25.1, async-20180527, dash-20180910,
git-commit-20181104, magit-popup-20181003,
with-editor-20181103
Summary: A Git porcelain inside Emacs.
Magit is an interface to the version
control system Git, implemented as an Emacs
package. Magit aspires to be a complete Git
porcelain. While we cannot (yet) claim,
that Magit wraps and improves upon each and
every Git command, it is complete enough to
allow even experienced Git users to perform
almost all of their daily version control
tasks directly from within Emacs.
While many fine Git clients exist, only
Magit and Git itself deserve to be
called porcelains.
> A question: several other packages were mention
> in the Magit description. Are these installed
> automatically when using the melpa interface
> in emacs ?
You mean the "Requires:" stuff? Yes, they are
installed when you install Magit (hit the
install button).
That is a big part of the whole idea with
a package manager and a software repository.
Every package says I rely on A, B, and C, then
A, B, and C say they rely on etc etc and
hopefully at some point there is no more
relying and the installation is complete and
everything put into place in good order.
In theory, it is very simple :)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2019-02-08 0:38 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 [this message]
2019-02-08 0:50 ` jonetsu
2019-02-08 1:14 ` Alexis
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=86imxv5d2s.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--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).