From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25590@debbugs.gnu.org
Subject: bug#25590: Remove build number from emacs-version variable
Date: Mon, 6 Feb 2017 13:34:40 -0500 [thread overview]
Message-ID: <CAM-tV-_=qQuWVVuBqGWmoiZOVSigU6m8P=juhNo9epq8nne28A@mail.gmail.com> (raw)
In-Reply-To: <83k29372t6.fsf@gnu.org>
On Mon, Feb 6, 2017 at 10:32 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Glenn Morris <rgm@gnu.org>
>> Cc: 25590@debbugs.gnu.org
>> Date: Sun, 05 Feb 2017 18:45:34 -0500
>>
>> Eli Zaretskii wrote:
>>
>> > If we do the above, we should make sure version-comparison functions
>> > treat something like "25.2 (build 4)" correctly.
>>
>> I disagree that this is desirable.
>
> Can you explain why? My reasoning was that if "25.2.4" is replaced by
> "25.2 (build 4)", then Lisp code that compares version (e.g., I have
> such code in my .emacs) will not work properly unless the
> version-comparison functions are updated to support such values.
I think the proposal is to go from this:
emacs-version ;=> "24.5.1"
(emacs-version) ;=> "GNU Emacs 24.5.1 (i686-pc-mingw32)
of 2015-04-11 on LEG570"
to this
emacs-version ;=> "24.5"
emacs-build-number ;=> 1
(emacs-version) ;=> "GNU Emacs 24.5 (Build 1) (i686-pc-mingw32)
of 2015-04-11 on LEG570"
i.e., there are no changes in version-comparibility:
(version< emacs-version "24.5") continues to work,
(version< (emacs-version) "24.5") continues to fail.
>
>> > It's actually part of a version number (which many other projects
>> > have, e.g., GDB just released version 7.12.1), except that we never
>> > release such versions, they exist only on end-users' machines. Other
>> > than that, there's nothing in it which is special to Emacs.
>>
>> I don't understand the comparison. A micro version number
>> (major.minor.micro) is not the same thing as Emacs's build number.
>
> I think it is.
>
GDB 7.12.1 is a public release, the official NEWS file documents the
differences between that and 7.12. For Emacs, there is no well-defined
difference between 25.1.1 and 25.1.2, it could be different for every
person who builds it.
next prev parent reply other threads:[~2017-02-06 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 17:55 bug#25590: Remove build number from emacs-version variable Glenn Morris
2017-02-04 10:15 ` Eli Zaretskii
2017-02-05 23:45 ` Glenn Morris
2017-02-06 15:32 ` Eli Zaretskii
2017-02-06 18:34 ` Noam Postavsky [this message]
2017-02-06 19:38 ` Eli Zaretskii
2017-02-06 20:24 ` Noam Postavsky
2017-02-07 4:40 ` Glenn Morris
2017-02-07 6:23 ` Glenn Morris
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='CAM-tV-_=qQuWVVuBqGWmoiZOVSigU6m8P=juhNo9epq8nne28A@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=25590@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.