From: Lars Ingebrigtsen <larsi@gnus.org>
To: Carson Chittom <carson@wistly.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Gnus version in emacs 24.1
Date: Wed, 05 Sep 2012 18:15:02 +0200 [thread overview]
Message-ID: <87ligo78ft.fsf@gnus.org> (raw)
In-Reply-To: <mailman.2904.1339801460.855.info-gnus-english@gnu.org> (Carson Chittom's message of "Fri, 15 Jun 2012 18:04:02 -0500")
Carson Chittom <carson@wistly.net> writes:
> Not that it matters particularly, but I'm curious--is there a reason the
> version wasn't incremented?
Yes, but the reason is really stupid, so I'd rather not say. :-)
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2012-09-05 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 6:06 Prateek Sadhukhan
2012-06-12 6:41 ` Kevin Brubeck Unhammer
2012-06-12 6:46 ` Lars Magne Ingebrigtsen
2012-06-15 23:04 ` Carson Chittom
[not found] ` <mailman.2904.1339801460.855.info-gnus-english@gnu.org>
2012-09-05 16:15 ` Lars Ingebrigtsen [this message]
2012-09-07 8:39 ` Peter Münster
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=87ligo78ft.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=carson@wistly.net \
--cc=info-gnus-english@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).