all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 25590@debbugs.gnu.org
Subject: bug#25590: Remove build number from emacs-version variable
Date: Sat, 04 Feb 2017 12:15:33 +0200	[thread overview]
Message-ID: <83r33e8doa.fsf@gnu.org> (raw)
In-Reply-To: <1svasvru4x.fsf@fencepost.gnu.org> (message from Glenn Morris on Tue, 31 Jan 2017 12:55:58 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Date: Tue, 31 Jan 2017 12:55:58 -0500
> 
> I'd like to suggest removing the build number from the variable emacs-version.
> Instead, it can go in a separate variable (eg emacs-build-number).
> The function emacs-version can still include it in parentheses, like it
> does for several other quantities.

If we do the above, we should make sure version-comparison functions
treat something like "25.2 (build 4)" correctly.

> Motivation:
> I think the build number is a largely internal detail that is only of
> interest to a small number of developers (as a data point, I've never
> used/wanted it for anything). Having it in the version string is
> confusing to people not familiar with Emacs development.

FWIW, I think this is a low-priority issue, as it most probably will
require quite a few changes, while the benefits are minor at best.

> (I am not aware of any other software that even has a concept of "build
> number".)

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.





  reply	other threads:[~2017-02-04 10:15 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 [this message]
2017-02-05 23:45   ` Glenn Morris
2017-02-06 15:32     ` Eli Zaretskii
2017-02-06 18:34       ` Noam Postavsky
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=83r33e8doa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25590@debbugs.gnu.org \
    --cc=rgm@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.