From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63956@debbugs.gnu.org, Jeff Norden <norden.jeff@gmail.com>,
sds@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#63956: 29.0.91; tex-mode display problem in emacs-29
Date: Sat, 10 Jun 2023 12:55:05 +0000 [thread overview]
Message-ID: <3c82fb01f423e31ef479@heytings.org> (raw)
In-Reply-To: <837csb2731.fsf@gnu.org>
>
> I don't know why this happens, perhaps due to differences in Git
> versions? I'm guessing you have some non-trivial setup of your email
> address for Git or something? The @amazon.com address wasn't just
> concocted by my Git client out of thin air, right?
>
> I tried on 2 other systems. One of them, with Git v2.34.1 reports what
> you see; the other, with Git 2.17.1, reports what I see.
>
The difference is that since Git 2.23.0 "git log" behaves by default as if
the --mailmap option was given, which uses the correspondence in the
.mailmap file. The actual author of commit 18b680cfd1 is sdsg@amazon.com,
but because of the line
Sam Steingold <sds@gnu.org> <sdsg@amazon.com>
in the .mailmap file the author is displayed as sds@gnu.org.
next prev parent reply other threads:[~2023-06-10 12:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 17:52 bug#63956: 29.0.91; tex-mode display problem in emacs-29 Jeff Norden
2023-06-08 9:15 ` Eli Zaretskii
2023-06-08 17:44 ` Sam Steingold
2023-06-08 18:34 ` Eli Zaretskii
2023-06-09 20:00 ` Sam Steingold
2023-06-10 5:56 ` Eli Zaretskii
2023-06-10 12:55 ` Gregory Heytings [this message]
2023-06-10 13:12 ` Eli Zaretskii
2023-06-10 13:20 ` Gregory Heytings
2023-06-11 6:22 ` Eli Zaretskii
2023-06-11 15:44 ` Jeff Norden
2023-06-11 16:01 ` Eli Zaretskii
2023-06-11 17:31 ` Jeff Norden
2023-06-11 18:14 ` Eli Zaretskii
2023-06-11 20:12 ` Jeff Norden
2023-06-12 11:49 ` Eli Zaretskii
2023-06-12 16:41 ` Jeff Norden
2023-06-12 16:44 ` Eli Zaretskii
2023-06-13 1:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-13 11:12 ` Eli Zaretskii
2023-06-09 16:30 ` Jeff Norden
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=3c82fb01f423e31ef479@heytings.org \
--to=gregory@heytings.org \
--cc=63956@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=norden.jeff@gmail.com \
--cc=sds@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).