[Top][All Lists]

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

bug#33328: 27.0.50; Extend Emacs bug report

From: Achim Gratz
Subject: bug#33328: 27.0.50; Extend Emacs bug report
Date: Thu, 22 Nov 2018 20:32:48 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Eli Zaretskii writes:
>> It is quite useless to ask which branch a given commit is on, since it
>> could be on any number of branches, only some of which might be shared
>> between your repo and the repo of the reporter.
> In general, yes.  But not in Emacs development, not with public
> development branches anyway.

You'd have to make a stipulation that the bug report must be made from
"public" branches only.  I don't think that'll work.  It's possible to
ask for the upstream branch that commit was in, which works until there
are intermediate clones used (i.e. the parent repo must be the public
one for it to work):

~/lisp/emacs-master> git branch -r --contains d2a07b9

So as long as you keep your own repo just one level away from the public
one, the commit is all you need to determine which branches it was
possibly on, but you still can't tell which exact branch was actually
checked out (if any tracking branches even existed at the local repo)
for any particular bug report.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:

reply via email to

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