From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Gnus v5.2 is released
Date: 28 May 1996 00:44:28 +0200 [thread overview]
Message-ID: <x6afytag8j.fsf@eyesore.no> (raw)
In-Reply-To: Steven L Baur's message of 26 May 1996 19:50:57 -0700
Steven L Baur <steve@miranova.com> writes:
> Could you separate out the Gnus version number from the rest of the
> string:
> "Gnus v5.2.1"
> Eg. Pull out the 5.2.1 (or whatever) into a separate variable?
I suppose. But shouldn't the alpha prefixes fit into the scheme?
`gnus-continuum-version' takes a Gnus version string and returns a
floating point number. September is greater than 5.1, and 5.2 is
greater than September, and Red is greater than 5.2, etc. (This
function is broken in 5.2.1, by the way.)
> (Or
> even something akin to emacs-major-version & emacs-minor-version).
> I'd like to be able to do things like:
> (concat "/usr/local/lib/xemacs/gnus-" gnus-version-number "/")
> or is there already a better way to do this?
Ok, I'll do this in 5.2.2.
> Also, once we move on into Red Gnus, will you reset the version
> numbering to 0 again, or use the Linux convention of even number
> stable, odd number development? Going to Red Gnus 5.3 might help
> reduce some confusion. And it might not, but it's worth asking.
I guess there will be a Gnus 5.2.0-5.2.15, and then I'll go to Gnus
5.3 for Emacs 19.32. Red Gnus will end up as 5.4 & 5.5, I guess.
(But the alphas will be "Red Gnus v0.1", etc., as with (ding) and
September.)
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-05-27 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-26 23:01 Lars Magne Ingebrigtsen
1996-05-27 1:23 ` Steven L Baur
1996-05-27 1:55 ` Lars Magne Ingebrigtsen
1996-05-27 2:50 ` Steven L Baur
1996-05-27 22:44 ` Lars Magne Ingebrigtsen [this message]
1996-05-28 1:39 ` Steven L Baur
1996-05-28 19:53 ` Lars Magne Ingebrigtsen
1996-05-28 2:17 ` Stephen Saroff
1996-05-28 15:08 ` Richard Pieri
2002-10-20 20:47 ` Carsten Leonhardt
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=x6afytag8j.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).