From: Steven L Baur <steve@miranova.com>
Cc: ding@ifi.uio.no
Subject: Re: Gnus v5.2 is released
Date: 26 May 1996 19:50:57 -0700 [thread overview]
Message-ID: <m2u3x2kewe.fsf@deanna.miranova.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 26 May 1996 18:55:21 -0700
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
Lars> Steven L Baur <steve@miranova.com> writes:
>> What's the difference between Sgnus 0.97 and Gnus 5.2.0 & Gnus 5.2.1?
Lars> The names? :-)
>> -rw-r--r-- 1 larsi 633523 May 26 22:45 sgnus-0.97.tar.gz
>> -rw-r--r-- 1 larsi 633518 May 26 22:54 gnus-5.2.0.tar.gz
>> -rw-r--r-- 1 larsi 637552 May 26 23:01 gnus-5.2.1.tar.gz
Lars> 5.2.0 and 0.97 are identical; 5.2.1 includes the etc/gnus-tut.txt
Lars> file but is otherwise the same as the other two.
O.K. I'm confused, but see the Gnus question in the soon-to-be
released XEmacs FAQ ;-).
http://www.miranova.com/~steve/xemacs-subsystems.html#Q4_2_1
While we're speaking of version numbers and transitions ...
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? (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?
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.
--
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-27 2:50 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 [this message]
1996-05-27 22:44 ` Lars Magne Ingebrigtsen
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=m2u3x2kewe.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).