public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Leif Lindholm <leif@nuviainc.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: devel@edk2.groups.io, philmd@redhat.com,
	Andrew Fish <afish@apple.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: Re: [PATCH] Maintainers: switch to my Arm email address
Date: Thu, 5 Mar 2020 15:33:27 +0100	[thread overview]
Message-ID: <30f05c26-b450-628a-d8f3-db5153d6f5df@redhat.com> (raw)
In-Reply-To: <20200305123017.GY23627@bivouac.eciton.net>

On 03/05/20 13:30, Leif Lindholm wrote:
> On Thu, Mar 05, 2020 at 12:23:46 +0100, Ard Biesheuvel wrote:
>> I no longer work for Linaro (and haven't for a while) so in anticipation
>> of losing access to my @linaro.org mailbox, let's switch to the ARM one
>> for my Tiancore contributions and maintainerships. Update the .mailmap
>> at the same time so the tooling can rewrite history where needed.
> 
> I have no issue either way, but I also don't think a proper decision
> was made last time around the .mailmap topic came up as to whether it
> was intended to span organisation changes.

We said that stewards wouldn't have the power to approve such, but the
subject contributors would.

> At present it does not in this project, and I would prefer for such a
> change to happen after an explicit policy decision rather than by
> accident.
> 
> In the meantime, for the Maintainers.txt changes:
> Reviewed-by: Leif Lindholm <leif@nuviainc.com>

I'm fine with both keeping and dropping the .mailmap hunk, as it is
being proposed by Ard.

So either way:

Reviewed-by: Laszlo Ersek <lersek@redhat.com>

Thanks
Laszlo


  reply	other threads:[~2020-03-05 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 11:23 [PATCH] Maintainers: switch to my Arm email address Ard Biesheuvel
2020-03-05 12:30 ` Leif Lindholm
2020-03-05 14:33   ` Laszlo Ersek [this message]
2020-03-31 10:22     ` Ard Biesheuvel

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-list 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=30f05c26-b450-628a-d8f3-db5153d6f5df@redhat.com \
    --to=devel@edk2.groups.io \
    /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