From: Eli Zaretskii <eliz@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: emacs-devel@gnu.org
Subject: Re: Enhancing (?) `emacs-version'
Date: Wed, 10 Feb 2016 22:33:47 +0200 [thread overview]
Message-ID: <83a8n89ufo.fsf@gnu.org> (raw)
In-Reply-To: <87vb5w71l1.fsf@mbork.pl> (message from Marcin Borkowski on Wed, 10 Feb 2016 21:27:38 +0100)
> From: Marcin Borkowski <mbork@mbork.pl>
> Cc: emacs-devel@gnu.org
> Date: Wed, 10 Feb 2016 21:27:38 +0100
>
> > We already have the variable emacs-repository-version, and
> > report-emacs-bug already includes it in the report.
>
> Thanks, I had no idea that this exists! What does it state for
> non-development versions (official, prebuilt pretests or binaries, for
> instance)?
The value is nil then.
> I guess it is (almost) good enough. I will probably advise
> emacs-version to include that info, though. Would it be helpful for the
> devs if I do? Not all bug-related messages are created with
> report-emacs-bug. Use case: a message to the bug-gnu-emacs list,
> stating that this-and-this bug can be reproduced on that-and-that Emacs
> version. It might be helpful for me if emacs-version included that info
> automatically.
IME, if the version is reported, it's reported by report-emacs-bug.
But maybe I misremember.
next prev parent reply other threads:[~2016-02-10 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 19:01 Enhancing (?) `emacs-version' Marcin Borkowski
2016-02-10 19:18 ` Óscar Fuentes
2016-02-10 19:24 ` Eli Zaretskii
2016-02-10 20:27 ` Marcin Borkowski
2016-02-10 20:33 ` Eli Zaretskii [this message]
2016-02-10 20:53 ` Marcin Borkowski
2016-02-10 22:30 ` Kaushal Modi
2016-02-10 22:37 ` Óscar Fuentes
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=83a8n89ufo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mbork@mbork.pl \
/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.