From: Thomas Koenig <tkoenig@netcologne.de>
To: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Correct my last name
Date: Tue, 8 Dec 2020 08:42:28 +0100 [thread overview]
Message-ID: <f27ef403-ec71-6dc2-9f22-ff788710731c@netcologne.de> (raw)
In-Reply-To: <5f1b4467-6d28-996b-c260-0cdb192bd79d@codesourcery.com>
Hi,
it seems that my last name is garbled for commits (see the mail below).
Would it be possible to change that to the alternate spelling "Thomas
Koenig"?
Best regards
Thomas
-------- Weitergeleitete Nachricht --------
Betreff: Re: git commits no longer visible on bugzilla?
Datum: Mon, 7 Dec 2020 10:12:48 +0100
Von: Tobias Burnus <tobias@codesourcery.com>
An: Thomas Koenig <tkoenig@netcologne.de>, gcc mailing list
<gcc@gcc.gnu.org>
Hi Thomas,
On 07.12.20 09:27, Tobias Burnus wrote:
> However, what puzzles me is
> https://gcc.gnu.org/pipermail/gcc-cvs/2020-December/338684.html –this
> is your commit. But while in the commit, I see "Koenig" for both
> 'Author' and 'Commit', the 'From:' of that email shows (at least in
> Pipermail) instead of 'oe' the Hindi letters 'tha' and 'Gh: '*थघ*'.
Seemingly, the hook (→ https://github.com/AdaCore/git-hooks) takes
the full name belonging to the user at gcc.gnu.org. And when
Richard checked it for me, for your name it returns (for his locale):
getent passwd tkoenig:
'Thomas Kथà¤'.
or passed through 'od':
…: T h o m a s K 340 244 245 340 244 230 n i g :…
If I didn't make a mistake, those numbers convert to hex:
E0 A3 A5 E0 A3 98
which I looks like garbage to me. At least it does not seem
to make sense in neither UTF-8, UTF-16, UTF-32 and I also
do not see any relation with the byte-order character.
I think there are two issues:
(a) Your name is wrong (should be 'ö' or safer 'oe')
→ I think you need to contact overseers via IRC or email
overseers@
(b) Non-ASCII should probably be accepted in the flow; it looks
as if the bugzilla email script mishandles/rejects this email
even though it contains valid Hindi letters.
Currently, the name comes from <git-hooks>/hooks/updates/emails.py:
self.email_from = '%s <%s@%s>' % (get_user_full_name(),
get_user_name(),
from_domain)
(those functions come from the 'utils' module.)
e_msg['From'] = sanitized_email_address(self.email_info.email_from)
(and this does a RFC2047 encoding)
Tobias
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München /
Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung,
Alexander Walter
next parent reply other threads:[~2020-12-08 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5f1b4467-6d28-996b-c260-0cdb192bd79d@codesourcery.com>
2020-12-08 7:42 ` Thomas Koenig [this message]
2020-12-08 12:43 ` Frank Ch. Eigler
2020-12-08 14:43 ` Thomas Koenig
2020-12-08 14:46 ` Frank Ch. Eigler
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=f27ef403-ec71-6dc2-9f22-ff788710731c@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=overseers@gcc.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.
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).