From: Richard Riley <rileyrg@googlemail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: nognus <ding@gnus.org>
Subject: Re: emacs 24 and gnus
Date: Tue, 04 Jan 2011 12:06:14 +0100 [thread overview]
Message-ID: <s4sjx9vsgp.fsf@news.eternal-september.org> (raw)
In-Reply-To: <8762u5c5iv.fsf@member.fsf.org> (Tassilo Horn's message of "Tue, 04 Jan 2011 11:44:24 +0100")
Tassilo Horn <tassilo@member.fsf.org> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
>> Whats the relationship, if any, between Gnus in Emacs 24 from bzr and
>> NoGnus? Will NoGnus from github become the Gnus that ships with Emacs
>> 24?
>
> The official Gnus repository is not on github, it is
> http://git.gnus.org/gnus.git. But anyway: the master branch of that
Ah yes, typo on my part. I almost think of git as "gitgub" now ...
> repository is synched with the emacs trunk regularily right now, so the
> Emacs 24.1 release will come with some version of NoGnus but rebranded
> to Gnus v5.13.
I have an urge to move to emacs 24 ... Yeah, I know, "why bother" but
its fun... I just wonder how far back my Gnus will then lag.
>
> At some point in time, there will be a feature freeze on the emacs
> branch for the 24.1 release, and then the Gnus git master branch will
> drift away from the version bundled in emacs.
>
> I hope that's more or less correct. ;-)
Thanks for the info. I'm sure it'll b e corrected by someone if not
correct ;)
btw, while you're there and without me digging around in the manual how
do I stop follow up (F) including my own email when I am cc'd? OK, I'll
go look in the manual ...
>
> Bye,
> Tassilo
cheers
r.
next prev parent reply other threads:[~2011-01-04 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 10:34 Richard Riley
2011-01-04 10:44 ` Tassilo Horn
2011-01-04 11:06 ` Richard Riley [this message]
2011-01-04 11:14 ` Adam Sjøgren
2011-01-04 11:58 ` Richard Riley
2011-01-04 12:04 ` Steinar Bang
2011-01-09 14:10 ` Tommy Kelly
2011-01-09 14:43 ` Richard Riley
2011-01-09 16:39 ` Tommy Kelly
2011-01-04 12:01 ` Tassilo Horn
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=s4sjx9vsgp.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding@gnus.org \
--cc=tassilo@member.fsf.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 NNTP newsgroup(s).