From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Gnus version numbers (was: Gnus 5.10 is now on the trunk)
Date: Thu, 09 Sep 2004 16:19:26 +0200 [thread overview]
Message-ID: <v9brgf34pd.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <buo4qm7sqe3.fsf@mctpc71.ucom.lsi.nec.co.jp> (Miles Bader's message of "Thu, 09 Sep 2004 19:11:48 +0900")
On Thu, Sep 09 2004, Miles Bader wrote:
> BTW, aren't we supposed to change the version number to "5.11" now?
I also thought about this.
I propose to add another minor version number: Let us set it to 5.11.1
now. After the release of Emacs 21.4, increase it again to 5.11.2 and
so on, so that each Emacs release also has a different Gnus version
(unless there are no changes in the Gnus code and manuals, maybe).
Rationale: In Emacs 21.1-21.3 all Gnus versions had 5.9 although the
Gnus version had significant differences.
E.g. `mm-coding-system-priorities' has been introduced in Emacs 21.2.
I don't remember how often I typed "if you have Gnus 5.9 that comes
with Emacs 21.2 or later you can set `mm-coding-system-priorities'
...".
Additionally, each time a new Emacs version is released, we could
release an unbundled Gnus version from the Gnus v5-10 branch.
Assuming that Gnus in Emacs' CVS and the Gnus v5-10 branch in sync, of
course. Lars, WDYT?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2004-09-09 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvwu04gc6f.fsf-monnier+emacs@gnu.org>
[not found] ` <x5y8kj3nn4.fsf@lola.goethe.zz>
[not found] ` <E1BvlwN-0003Hn-Ey@fencepost.gnu.org>
[not found] ` <v9ekm4r4rx.fsf@marauder.physik.uni-ulm.de>
[not found] ` <E1BxrIE-0004Nu-BO@fencepost.gnu.org>
[not found] ` <v93c24e1ky.fsf@marauder.physik.uni-ulm.de>
[not found] ` <20040831224603.GB6230@fencepost>
[not found] ` <v9wtzetom6.fsf@marauder.physik.uni-ulm.de>
[not found] ` <20040904132456.GA16964@fencepost>
[not found] ` <uwtz8m9ns.fsf@gnu.org>
[not found] ` <buohdqckszb.fsf@mctpc71.ucom.lsi.nec.co.jp>
[not found] ` <buo4qm7sqe3.fsf@mctpc71.ucom.lsi.nec.co.jp>
2004-09-09 14:19 ` Reiner Steib [this message]
2004-09-09 15:49 ` Gnus version numbers Lars Magne Ingebrigtsen
2004-09-10 12:29 ` Reiner Steib
2004-09-10 13:48 ` Lars Magne Ingebrigtsen
2004-09-10 17:49 ` Stefan Monnier
2004-09-10 18:04 ` Lars Magne Ingebrigtsen
2004-09-13 17:20 ` Reiner Steib
2004-09-13 18:29 ` Lars Magne Ingebrigtsen
2004-09-14 9:49 ` Per Abrahamsen
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=v9brgf34pd.fsf_-_@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=Reiner.Steib@gmx.de \
--cc=larsi@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).