From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: How to update core extensions (Gnus)?
Date: Tue, 03 Mar 2015 00:34:59 +0100 [thread overview]
Message-ID: <87h9u3rn18.fsf@debian.uxu> (raw)
In-Reply-To: mailman.1130.1425299050.31049.help-gnu-emacs@gnu.org
torys.anderson@gmail.com (Tory S. Anderson) writes:
> 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?
You know what they say in Barcelona: If you ever so
slightly considered taking a psychedelic drug - you
are thinking, "well, maybe" - then you should do it :)
I hope and think Gnus isn't stagnating. Gnus is part
of Emacs (it says "Version: 5.13" in gnus.el) so you
should get updates automagically with the next version
of Emacs.
What gnus.el version do you have? You can also echo
the `gnus-version' variable.
By the way, this is your second question about getting
the latest stuff in unorthodox ways. And you even use
Emacs 25.0 (I have 24.4). You are not neurotic about
this, now? :)
--
underground experts united
next parent reply other threads:[~2015-03-02 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1130.1425299050.31049.help-gnu-emacs@gnu.org>
2015-03-02 23:34 ` Emanuel Berg [this message]
2015-03-03 19:06 ` How to update core extensions (Gnus)? Tory S. Anderson
2015-03-02 12:23 Tory S. Anderson
2015-03-02 12:39 ` Glyn Millington
2015-03-02 12:52 ` Alan Schmitt
2015-03-03 1:34 ` Les Harris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9u3rn18.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.