From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Gnus version
Date: Tue, 01 Nov 2011 07:47:50 +0900 [thread overview]
Message-ID: <b4my5w0pyll.fsf@jpl.org> (raw)
BTW, hadn't we better bump the Gnus version number in Emacs?
Though I don't recall how to increment it. In ChangeLog:
2007-10-28 v5.13
2004-01-04 v5.10.6
2004-01-04 v5.10.5
2004-01-03 v5.10.4
2003-12-30 v5.10.3
2003-05-14 v5.10.2
2003-05-01 v5.10.1
1999-02-19 v5.6.46
1998-11-19 v5.6.45
next reply other threads:[~2011-10-31 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 22:47 Katsumi Yamaoka [this message]
2011-10-31 23:51 ` Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2016-05-27 7:46 gnus version Eric S Fraga
2016-05-27 17:15 ` Adam Sjøgren
[not found] ` <e46b3917bff14a3dbc1dee9dd44200cb@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-30 13:02 ` Eric S Fraga
2001-09-11 7:05 Gnus version Gurusami Annamalai
2001-09-11 17:35 ` Paul Jarc
2001-09-11 18:21 ` Bill White
2001-09-11 21:36 ` Steve Youngs
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=b4my5w0pyll.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-devel@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 NNTP newsgroup(s).