From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] .mailmap: map Kristoffer H.
Date: Tue, 29 Sep 2026 15:43:10 +0200 [thread overview]
Message-ID: <3ab2b1a8-8b2e-4469-8173-36118c826780@app.fastmail.com> (raw)
In-Reply-To: <xmqqy0clmlme.fsf@gitster.g>
On Mon, Sep 28, 2026, at 17:38, Junio C Hamano wrote:
> kristofferhaugsbakk@fastmail.com writes:
>
>> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>>
>> Map my email addresses for Fastmail and Gmail. Fastmail has been used
>> for some trailers and Gmail for my first four commits.
>>
>> The `code@` address is my canonical address here both for commits and
>> for trailers. I recently posted about that preference.[1] But I can do
>> more than state my preference, namely to make it possible to look up my
>> preferred name+email pair:
>>
>> git check-mailmap 'Kristoffer Haugsbakk <kristoffer.haugsbakk@gmail.com>'
>>
>> Which one can use as a trailer command via `trailer.<key-alias>.cmd`.
>>
>> † 1: https://lore.kernel.org/git/add1abaa-5d51-43dc-9907-d6d3851004f5@app.fastmail.com/
>>
>> That’s the only motivation for this change. The Gmail adddress is just
>> for completeness.
>>
>> Although the proper long-term solution would be to fix my domain so that
>> Gmail doesn’t think it is suspicious anymore.
>>
>> Assisted-by: GNU Emacs
>
> Is this an attempt to render use of Assisted-by trailers that we see
> more frequently these days less meaningful? ;-)
;)
Just a gag.
prev parent reply other threads:[~2026-09-29 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 7:15 [PATCH] .mailmap: map Kristoffer H kristofferhaugsbakk
2026-09-28 15:38 ` Junio C Hamano
2026-09-29 13:43 ` Kristoffer Haugsbakk [this message]
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=3ab2b1a8-8b2e-4469-8173-36118c826780@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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