From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 39940@debbugs.gnu.org
Subject: bug#39940: The variable operating-system-release
Date: Fri, 06 Mar 2020 09:42:34 +0200 [thread overview]
Message-ID: <835zfiudxx.fsf@gnu.org> (raw)
In-Reply-To: <5dblpawa8s.fsf@fencepost.gnu.org> (message from Glenn Morris on Thu, 05 Mar 2020 20:19:31 -0500)
> From: Glenn Morris <rgm@gnu.org>
> Date: Thu, 05 Mar 2020 20:19:31 -0500
>
> I found the variable 'operating-system-release' for the first time today.
>
> 1) This isn't what I would call the operating system release.
> Eg my current operating system is CentOS, release 8.1.
> operating-system-release is "4.18.0-147.5.1.el8_1.x86_64",
> which is the kernel version. (Surprising to find these two things
> mixed up in a GNU project. :) )
>
> 2) I don't see why it is useful to have a Lisp variable for this
> (it had one use in the Emacs C code before c996fe1ec6).
> I suggest obsoleting it.
(My Git repository doesn't know about commit c996fe1ec6. AFAICT, this
variable was added in 3bb9abc.)
Some relevant information:
This variable was added due to the issues discussed in this old
thread:
https://lists.gnu.org/archive/html/emacs-devel/2005-01/msg00629.html
See also
https://lists.gnu.org/archive/html/emacs-devel/2005-01/msg00835.html
(I guess I never got any responses, and so the documentation never
happened ;-)
next prev parent reply other threads:[~2020-03-06 7:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 1:19 bug#39940: The variable operating-system-release Glenn Morris
2020-03-06 7:42 ` Eli Zaretskii [this message]
2021-01-29 6:26 ` Lars Ingebrigtsen
2021-01-29 9:30 ` Glenn Morris
2021-01-30 6:10 ` Lars Ingebrigtsen
2021-01-30 8:38 ` Eli Zaretskii
2021-01-31 7:24 ` Lars Ingebrigtsen
2021-01-31 13:06 ` Basil L. Contovounesios
2021-01-31 15:07 ` Eli Zaretskii
2021-02-01 3:21 ` Basil L. Contovounesios
2021-02-01 3:37 ` Eli Zaretskii
2021-02-01 8:25 ` Lars Ingebrigtsen
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=835zfiudxx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39940@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.