From: Drew Adams <drew.adams@oracle.com>
To: Deric Bytes <dericbytes@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: Is it worth leaving el-get for melpa
Date: Fri, 3 Nov 2017 16:19:19 -0700 (PDT) [thread overview]
Message-ID: <d3f8a936-c725-4b58-9cbc-d9da5d20242f@default> (raw)
In-Reply-To: <b04708b1-2a81-46cf-a8a5-f35897d56cd2@googlegroups.com>
> I am using el-get, should I just stick with it or move it all over to
> melpa.
>
> Do I gain or lose anything from switching?
> Can I easily select the latest git repos through the melpa interface?
> Anyone else made the switch from being a dedicated el-get user to melpa?
This Emacs-Wiki page speaks to some of the differences:
https://www.emacswiki.org/emacs/el-get
next prev parent reply other threads:[~2017-11-03 23:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 22:50 Is it worth leaving el-get for melpa Deric Bytes
2017-11-03 23:19 ` Drew Adams [this message]
[not found] ` <mailman.2874.1509751172.27995.help-gnu-emacs@gnu.org>
2017-11-04 0:44 ` Deric Bytes
2017-11-04 5:54 ` N. Raghavendra
[not found] ` <mailman.2882.1509774912.27995.help-gnu-emacs@gnu.org>
2017-11-04 16:04 ` Deric Bytes
2017-11-04 0:55 ` Deric Bytes
2017-11-04 22:57 ` Emanuel Berg
2017-11-09 21:47 ` Eric S Fraga
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=d3f8a936-c725-4b58-9cbc-d9da5d20242f@default \
--to=drew.adams@oracle.com \
--cc=dericbytes@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).