bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#33328: 27.0.50; Extend Emacs bug report


From: Michael Albinus
Subject: bug#33328: 27.0.50; Extend Emacs bug report
Date: Wed, 21 Nov 2018 13:46:49 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Glenn Morris <address@hidden> writes:

Hi Glenn,

>> 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.

A version number is not sufficient. It depends, which branch is checked
out. See for example

--8<---------------cut here---------------start------------->8---
# ( cd ~/src/emacs ; git name-rev d2a07b9a82a632e8baa179c667a98d275e5f6973 )
d2a07b9a82a632e8baa179c667a98d275e5f6973 
remotes/origin/scratch/accurate-warning-pos~44

# ( cd ~/src/emacs-test ; git name-rev d2a07b9a82a632e8baa179c667a98d275e5f6973 
)
d2a07b9a82a632e8baa179c667a98d275e5f6973 remotes/origin/HEAD~89
--8<---------------cut here---------------end--------------->8---

The former is a master checkout, the latter is a
feature/tramp-thread-safe checkout. Just the revision
d2a07b9a82a632e8baa179c667a98d275e5f6973 doesn't tell me the branch the
original bug report has been written for.

Best regards, Michael.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]