From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Cc: ding@gnus.org
Subject: Re: Gnus version numbers
Date: Fri, 10 Sep 2004 14:29:49 +0200 [thread overview]
Message-ID: <v9acvy71du.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3656ntpbb.fsf@quimbies.gnus.org>
On Thu, Sep 09 2004, Lars Magne Ingebrigtsen wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>
>> 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?
>
> Sounds good.
One possible problem with using the additional minor number (5.11.1
instead of 5.11) is that `gnus-continuum-version' of 5.11.1 is greater
than that of all No Gnus versions:
ELISP> (gnus-continuum-version "No Gnus v0.3")
5.110003
ELISP> (gnus-continuum-version "Gnus v5.11.1")
5.1101
ELISP> (gnus-continuum-version "Gnus v5.11")
5.11
I don't know how problematic this would be, but I would think that all
No Gnus versions should be higher than the 5.11* versions. A simple
(but ugly?) solution would be to change the set the version to
5.11MMNN for "No Gnus v0.NN" with MM in (01...99).
With MM=90: "No Gnus v0.3" ==> 5.119003
"No Gnus v0.12" ==> 5.119012
With MM=99: "No Gnus v0.3" ==> 5.119903
"No Gnus v0.12" ==> 5.119912
Might be a little confusion for the user, but I don't think that users
are supposed to look at the continuum version at all.
Other suggestions?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-09-10 12:29 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 ` Gnus version numbers (was: Gnus 5.10 is now on the trunk) Reiner Steib
2004-09-09 15:49 ` Gnus version numbers Lars Magne Ingebrigtsen
2004-09-10 12:29 ` Reiner Steib [this message]
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=v9acvy71du.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=Reiner.Steib@gmx.de \
--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).