From: Steven L Baur <steve@miranova.com>
Cc: ding@ifi.uio.no
Subject: Re: Gnus v5.2 is released
Date: 27 May 1996 18:39:00 -0700 [thread overview]
Message-ID: <m2ohn9shjf.fsf@deanna.miranova.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 27 May 1996 15:44:28 -0700
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
Lars> 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?
Lars> I suppose. But shouldn't the alpha prefixes fit into the scheme?
Yes. I'm interested in something I can reference at runtime that will
help me find the gnus source tree, which means something I can map
back to sgnus-0.97/*, or gnus-5.2.1/*, or rgnus-0.11/*.
Lars> `gnus-continuum-version' takes a Gnus version string and returns a
Lars> floating point number. September is greater than 5.1, and 5.2 is
Lars> greater than September, and Red is greater than 5.2, etc. (This
Lars> function is broken in 5.2.1, by the way.)
I wasn't aware of this function. This is very nice, but not exactly
what I was asking for. It doesn't look like 5.0.14 and 5.0.15 (which
came after 5.1) are treated correctly.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
next prev parent reply other threads:[~1996-05-28 1:39 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
1996-05-28 1:39 ` Steven L Baur [this message]
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=m2ohn9shjf.fsf@deanna.miranova.com \
--to=steve@miranova.com \
--cc=ding@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).