From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [Suggestion] New function `emacs-version>='
Date: Tue, 6 May 2003 16:45:48 -0500 (CDT) [thread overview]
Message-ID: <200305062145.h46Ljmf24686@eel.dms.auburn.edu> (raw)
In-Reply-To: <67B8CED503F3D511BB9F0008C75DAD66054855D6@dewdfx17> (christoph.wedler@sap.com)
Chris Wedler wrote:
I thought it would be the 3rd number in `emacs-version' because the
Emacs-21.3 pre-releases had a useful numering scheme, i.e., they had
versions 21.2.90, 21.2.91, ...
I do not see why a package developer would want to support old
pre-releases. It seems to me that pre-releases become obsolete once
the actual version is released.
Since there might be some bug-fix releases of Emacs-21.3 before
Emacs-21.4 is out,
I believe that Emacs-21.3 is itself a bug-fix release.
I would think it would be useful to have versions numbers 21.3.0,
21.3.1 etc for them. How do I distinguish between such Emacs-21.3
versions now?
In as far as I know, there is only one version of Emacs-21.3. Except
that the user could build several different versions, using different
toolkits or whatever. These will get different third numbers, but
only the user knows the meaning of that third number.
Or is the first bug fix of Emacs-21.3 called
Emacs-21.4 (and the second Emacs-21.5)?
Yes. Unless there are new-feature releases in between.
I would also have guessed something similar for the Emacs development
version... (e.g., that they start with Emacs-21.3.40 or whatever...)
The current CVS is Emacs-21.3.50. You get a fourth number telling you
how many times you built it.
Essentially, the information you want from `emacs-patch-level' is
already contained in `emacs-minor-version'. You just wind up with
more minor-versions, since each bug-fix release increments
`emacs-minor-version'.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-05-06 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 11:10 [Suggestion] New function `emacs-version>=' Wedler, Christoph
2003-05-06 21:45 ` Luc Teirlinck [this message]
2003-05-07 11:51 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 12:11 Wedler, Christoph
2003-05-07 12:46 ` Luc Teirlinck
2003-05-09 11:19 ` Richard Stallman
2003-05-02 19:55 Wedler, Christoph
2003-05-02 21:16 ` Thien-Thi Nguyen
2003-05-04 13:03 ` Richard Stallman
2003-05-05 12:52 ` Wedler, Christoph
2003-05-05 13:20 ` Juanma Barranquero
2003-05-05 19:11 ` Richard Stallman
2003-05-05 21:59 ` Luc Teirlinck
2003-05-06 23:42 ` Istvan Marko
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200305062145.h46Ljmf24686@eel.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).