unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Wedler, Christoph" <christoph.wedler@sap.com>
Cc: emacs-devel@gnu.org
Subject: RE: [Suggestion] New function `emacs-version>='
Date: Tue, 6 May 2003 13:10:53 +0200	[thread overview]
Message-ID: <67B8CED503F3D511BB9F0008C75DAD66054855D6@dewdfx17> (raw)

Luc Teirlinck wrote:
 > Christoph Wedler wrote:

 >    (a constant `emacs-patch-level' would be useful then)

 > What would that constant represent?

Well, some emacs-minor-minor-version ;-)  I don't know the current Emacs
version numering scheme.

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, ...

Since there might be some bug-fix releases of Emacs-21.3 before
Emacs-21.4 is out, 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?  Or is the first bug fix of Emacs-21.3 called
Emacs-21.4 (and the second Emacs-21.5)?

I would also have guessed something similar for the Emacs development
version... (e.g., that they start with Emacs-21.3.40 or whatever...)

 > From the code of emacs-version>= you proposed, it would seem that it
 > would be say the "2" in emacs-21.3.2, representing the second
 > instance of 21.3 the user built in the given directory, or the "50",
 > in emacs-21.3.50.43 (or whatever).  If so, patch-level 50 for
 > emacs-21.3 could represent the 50th time that a "compulsive Emacs
 > builder" built Emacs-21.3 or it could represent a snapshot of
 > emacs-21.3.50.

Err, obviously, Emacs has a different the numering scheme...

 > That would not seem to make a whole lot of sense.

Indeed, but it could make sense if adopted to the Emacs version numering
scheme (which might need to be defined).

- Christoph

             reply	other threads:[~2003-05-06 11:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 11:10 Wedler, Christoph [this message]
2003-05-06 21:45 ` [Suggestion] New function `emacs-version>=' Luc Teirlinck
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=67B8CED503F3D511BB9F0008C75DAD66054855D6@dewdfx17 \
    --to=christoph.wedler@sap.com \
    --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).