[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33328: 27.0.50; Extend Emacs bug report
From: |
Glenn Morris |
Subject: |
bug#33328: 27.0.50; Extend Emacs bug report |
Date: |
Tue, 20 Nov 2018 14:00:35 -0500 |
User-agent: |
Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) |
Michael Albinus wrote:
>> Sorry for the slow reply, but given the hash from emacs-repository-version,
>> doesn't a command like "git name-rev HASH" give you this information,
>> without you needing to store extra information in the Emacs binary?
>
> Anything goes of course, but is it really a problem? A short string
> shouldn't hurt.
The code to implement this doesn't seem that small, and seems redundant
to me.
http://lists.gnu.org/r/emacs-diffs/2018-11/msg00072.html
> I use this kind of information also in Tramp (see variable
> tramp-repository-branch), and it would be an additional burden always to
> use call-process for just opening a new debug buffer.
I meant, when you get a bug report, if you care which branch it came
from, and it isn't obvious from the version number, just use
git name-rev to find out. You will presumably be looking at the git log
anyway for debugging.
- bug#33328: 27.0.50; Extend Emacs bug report, Michael Albinus, 2018/11/09
- bug#33328: 27.0.50; Extend Emacs bug report, Glenn Morris, 2018/11/15
- bug#33328: 27.0.50; Extend Emacs bug report, Michael Albinus, 2018/11/15
- bug#33328: 27.0.50; Extend Emacs bug report, Achim Gratz, 2018/11/22
- bug#33328: 27.0.50; Extend Emacs bug report, Eli Zaretskii, 2018/11/22
- bug#33328: 27.0.50; Extend Emacs bug report, Eli Zaretskii, 2018/11/22
- bug#33328: 27.0.50; Extend Emacs bug report, Achim Gratz, 2018/11/22
- bug#33328: 27.0.50; Extend Emacs bug report, Michael Albinus, 2018/11/22
- bug#33328: 27.0.50; Extend Emacs bug report, Achim Gratz, 2018/11/25
- bug#33328: 27.0.50; Extend Emacs bug report, Michael Albinus, 2018/11/25