From: Achim Gratz <Stromeko@nexgo.de>
To: 33328@debbugs.gnu.org
Subject: bug#33328: 27.0.50; Extend Emacs bug report
Date: Sun, 25 Nov 2018 12:21:03 +0100 [thread overview]
Message-ID: <875zwlmmhs.fsf@Rainer.invalid> (raw)
In-Reply-To: <87pnvdgah9.fsf@gmx.de>
Michael Albinus writes:
> There is a useful answer. If it tells me a branch name which is not
> public, I know that I even cannot trust "emacs -Q" behavior. I will
> continue with more inquisitorial questions :-)
No it doesn't. Again, branch names are local things and may or may not
match up with upstream, whether you like it or not. The commit id is
telling you that you are still looking at the same checkout that you
have (or not if there actually are local changes).
> Fortunately, most of the time this is not necessary 'cos people use
> publich branches.
Nope. If you want to correlate commit id to branch names in the way you
expect to, you need to do it in a repo _you_ control.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2018-11-25 11:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 22:19 bug#33328: 27.0.50; Extend Emacs bug report Michael Albinus
2018-11-10 7:47 ` Eli Zaretskii
2018-11-10 8:57 ` Michael Albinus
2018-11-10 9:49 ` Eli Zaretskii
2018-11-10 15:09 ` Michael Albinus
2018-11-15 17:45 ` Glenn Morris
2018-11-15 20:31 ` Michael Albinus
2018-11-20 19:00 ` Glenn Morris
2018-11-21 12:46 ` Michael Albinus
2018-11-22 18:52 ` Glenn Morris
2018-11-22 19:08 ` Eli Zaretskii
2018-11-22 19:14 ` Achim Gratz
2018-11-22 19:22 ` Eli Zaretskii
2018-11-22 19:31 ` Eli Zaretskii
2018-11-22 19:36 ` Achim Gratz
2018-11-22 21:52 ` Michael Albinus
2018-11-25 11:21 ` Achim Gratz [this message]
2018-11-25 11:46 ` Michael Albinus
2018-11-23 8:14 ` Eli Zaretskii
2018-11-22 19:32 ` Achim Gratz
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=875zwlmmhs.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=33328@debbugs.gnu.org \
/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.