From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Re: synchronizing with Emacs, take two
Date: Wed, 30 Jun 2010 22:34:55 -0400 [thread overview]
Message-ID: <841vbond4g.fsf@incoming.verizon.net> (raw)
In-Reply-To: <b4mwrtgymr2.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 01 Jul 2010 11:11:29 +0900")
> BTW, is `No Gnus' really necessary? Though I've been maintaining
> it so as to work with various version of Emacsen, I don't know
> whether there are really a lot of people who use it. People who
> want the most recent Gnus can upgrade Emacs (if needed, even to
> use the Emacs head is not so troublesome). The only point may be
> that the Gnus XEmacs package is very old (it is now Gnus 5.10.8).
It is for this XEmacs user, for the exact reason you mention. Of
course I don't care whether you continue to call in No Gnus or turn it
into some other naming scheme if that makes it easier for the
maintainers. I do take advantage of several of the features, SMIME
related in particular, that are not available in the older versions.
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2010-07-01 2:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3zl51tzgl.fsf@fleche.redhat.com>
[not found] ` <87zl07ynxi.fsf@gate450.dyndns.org>
[not found] ` <mailman.7.1273778942.8369.bug-gnu-emacs@gnu.org>
2010-06-30 21:35 ` bug#5284: 23.1; gnus-summary-expire-thread does not work Ted Zlatanov
2010-06-30 21:46 ` synchronizing with Emacs, take two Ted Zlatanov
2010-07-01 2:11 ` Katsumi Yamaoka
2010-07-01 2:34 ` Dave Goldberg [this message]
2010-07-01 13:59 ` Ted Zlatanov
2010-07-02 3:57 ` Katsumi Yamaoka
2010-07-04 22:26 ` Mike Kupfer
2010-08-12 20:50 ` Ted Zlatanov
2011-02-25 22:07 ` Ted Zlatanov
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=841vbond4g.fsf@incoming.verizon.net \
--to=david.goldberg6@verizon.net \
--cc=ding@gnus.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).