bug#33328: 27.0.50; Extend Emacs bug report

[Achim Gratz <Stromeko@nexgo.de>]

Michael Albinus writes:
> A version number is not sufficient. It depends, which branch is checked
> out. See for example

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.

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

~/lisp/emacs-master> git branch --contains d2a07b9
* blafasel
  master

I've just created and checked out a new branch blafasel, then asked git
to name the (local) branches that have this commit.  I generally don't
pull feature branches and similar namespaces, but almost always work on
local branches.

> # ( cd ~/src/emacs-test ; git name-rev d2a07b9a82a632e8baa179c667a98d275e5f6973 )
> d2a07b9a82a632e8baa179c667a98d275e5f6973 remotes/origin/HEAD~89
>
> 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.

So, what information would you gain if you learned it was branch
"blafasel"?


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

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra