From: torys.anderson@gmail.com (Tory S. Anderson)
To: Emacs Help List <help-gnu-emacs@gnu.org>
Subject: How to update core extensions (Gnus)?
Date: Mon, 02 Mar 2015 07:23:56 -0500 [thread overview]
Message-ID: <87wq2z610j.fsf@gmail.com> (raw)
Contrary to my long-held belief in the stagnation of the Gnus codebase (I was under the impression it had been untouched since 2009), Gnus has been revived and I want to implement changes that are newer than my current 25.0.5 emacs version. But it looks from my package manager that Gnus isn't something that I can, for instance, grab from Melpa. What's the best practice for updating a core package like this? Can I clone http://git.gnus.org/gnus.git and cause emacs to respect the clone over the built-in? Should I?
next reply other threads:[~2015-03-02 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 12:23 Tory S. Anderson [this message]
2015-03-02 12:39 ` How to update core extensions (Gnus)? Glyn Millington
2015-03-02 12:52 ` Alan Schmitt
2015-03-03 1:34 ` Les Harris
[not found] <mailman.1130.1425299050.31049.help-gnu-emacs@gnu.org>
2015-03-02 23:34 ` Emanuel Berg
2015-03-03 19:06 ` Tory S. Anderson
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=87wq2z610j.fsf@gmail.com \
--to=torys.anderson@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).