git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: emilyshaffer@google.com
Cc: git@vger.kernel.org, Emily Shaffer <nasamuffin@google.com>
Subject: Re: [PATCH] mailmap: change primary address for Emily Shaffer
Date: Fri, 07 Apr 2023 14:35:09 -0700	[thread overview]
Message-ID: <xmqq5ya7jrzm.fsf@gitster.g> (raw)
In-Reply-To: <20230407212249.1541509-1-nasamuffin@google.com> (emilyshaffer@google.com's message of "Fri, 7 Apr 2023 14:22:49 -0700")

emilyshaffer@google.com writes:

> From:   emilyshaffer@google.com
> Subject: [PATCH] mailmap: change primary address for Emily Shaffer
>
> Emily finally figured out how to set up their alias at DayJob, and would
> prefer to use nasamuffin@google.com, partially to reduce confusion
> between IRC and list, and partially because they just like the alias a
> lot more.
>
> Signed-off-by: Emily Shaffer <nasamuffin@google.com>
> ---
>  .mailmap | 1 +
>  1 file changed, 1 insertion(+)

Cute.  By telling the machinery to map "<emilyshaffer@google.com>"
(with any name) to "Emily Shaffer <nasamuffin@google.com>", and
using a nameless <emilyshaffer@google.com> as the sender for the
mail to add such a mailmap entry, the result of applying such a
patch, even though the underlying commit object created lacks the
human-readable name, like so:

    $ git cat-file commit HEAD
    tree cec72ed0d4fb9faa44cd8d23008f90da3239808b
    parent 0607f793cbe0af16aee6d2480056d891835884bd
    author emilyshaffer@google.com <emilyshaffer@google.com> 1680902569 -0700
    committer Junio C Hamano <gitster@pobox.com> 1680902794 -0700

    mailmap: change primary address for Emily Shaffer
    ...

would show with a substituted author:

    $ git show HEAD
    commit 2485a52e4b4419020286e98dd04c0e5ebb218f06
    Author: Emily Shaffer <nasamuffin@google.com>
    Date:   Fri Apr 7 14:22:49 2023 -0700

        mailmap: change primary address for Emily Shaffer
        ...    

I'll amend the commit to record the nasammuffin name instead,
though.



  reply	other threads:[~2023-04-07 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 21:22 [PATCH] mailmap: change primary address for Emily Shaffer emilyshaffer
2023-04-07 21:35 ` Junio C Hamano [this message]
2023-04-07 21:58   ` Emily Shaffer

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq5ya7jrzm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.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).