From: Sivaram Neelakantan <nsivaram.net@gmail.com>
To: ding@gnus.org
Subject: Re: Gnus version recent enough ?
Date: Thu, 05 May 2022 19:50:06 +0530 [thread overview]
Message-ID: <85bkwcm57t.fsf@gmail.com> (raw)
In-Reply-To: <87bkwdnx06.fsf@ucl.ac.uk>
On Wed, May 04 2022,Eric S Fraga wrote:
> On Wednesday, 4 May 2022 at 16:28, Robert Pluim wrote:
>> Thatʼs one option, or we could just bump the gnus version everytime
>> Emacs is released. Lars?
>
> If gnus is now part of Emacs, and its development and release coincide
> with Emacs's own, should it actually have a version number at all?
Good point. I second this, it should be dropped to prevent any
confusion over what version is packaged with what emacs release.
sivaram
--
prev parent reply other threads:[~2022-05-05 14:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 13:15 Erik Colson
2022-05-04 13:18 ` Robert Pluim
2022-05-04 13:31 ` Erik Colson
2022-05-04 14:16 ` Sam Steingold
2022-05-04 14:28 ` Robert Pluim
2022-05-04 15:22 ` Eric S Fraga
2022-05-04 16:03 ` Adam Sjøgren
2022-05-04 17:54 ` Eric S Fraga
2022-05-04 19:11 ` Sam Steingold
2022-05-04 19:20 ` Emanuel Berg
2022-05-05 8:03 ` Eric S Fraga
2022-05-05 4:19 ` Pankaj Jangid
2022-05-05 15:59 ` Andreas Schwab
2022-05-05 17:18 ` Sam Steingold
2022-05-06 3:11 ` Pankaj Jangid
2022-05-05 14:20 ` Sivaram Neelakantan [this message]
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=85bkwcm57t.fsf@gmail.com \
--to=nsivaram.net@gmail.com \
--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).