From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 33328@debbugs.gnu.org, michael.albinus@gmx.de
Subject: bug#33328: 27.0.50; Extend Emacs bug report
Date: Thu, 22 Nov 2018 21:08:07 +0200 [thread overview]
Message-ID: <83efbdgcbs.fsf@gnu.org> (raw)
In-Reply-To: <987eh53px1.fsf@fencepost.gnu.org> (message from Glenn Morris on Thu, 22 Nov 2018 13:52:58 -0500)
> From: Glenn Morris <rgm@gnu.org>
> Date: Thu, 22 Nov 2018 13:52:58 -0500
> Cc: 33328@debbugs.gnu.org
>
> Thanks for the example, name-rev clearly isn't doing what I thought. I
> would still think the branch information would be derivable from the
> hash, eg https://github.com/mhagger/git-when-merged , but clearly it's
> not so simple.
Branches mean nothing to Git.
next prev parent reply other threads:[~2018-11-22 19:08 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83efbdgcbs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33328@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=rgm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).