public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif@nuviainc.com>
To: devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH 0/2] Maintainers.txt (new year, new me)
Date: Mon, 7 Feb 2022 11:46:23 +0000	[thread overview]
Message-ID: <YgEGj/IAhpbg9izl@leviathan> (raw)
In-Reply-To: <20220131114042.1619459-1-leif@nuviainc.com>

On Mon, Jan 31, 2022 at 11:40:40 +0000, Leif Lindholm wrote:
> The first patch adds some missing github IDs spotted when preparing the
> second patch.
> 
> The second patch changes my email address from NUVIA to Qualcomm
> Innovation Center (Quicinc).
> 
> Cc: Andrew Fish <afish@apple.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Leif Lindholm <quic_llindhol@quicinc.com>

Thanks - merged as 96b8b5fd108a..1f54eaa725f4.

> Leif Lindholm (2):
>   Maintainers.txt: add missing github IDs to OvmfPkf/Fdt reviewers
>   Maintainers.txt: update email for Leif Lindholm
> 
>  Maintainers.txt | 20 ++++++++++----------
>  1 file changed, 10 insertions(+), 10 deletions(-)
> 
> -- 
> 2.30.2
> 

      parent reply	other threads:[~2022-02-07 11:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 11:40 [PATCH 0/2] Maintainers.txt (new year, new me) Leif Lindholm
2022-01-31 11:40 ` [PATCH 1/2] Maintainers.txt: add missing github IDs to OvmfPkf/Fdt reviewers Leif Lindholm
2022-02-01 13:21   ` [edk2-devel] " Gerd Hoffmann
2022-01-31 11:40 ` [PATCH 2/2] Maintainers.txt: update email for Leif Lindholm Leif Lindholm
2022-01-31 11:43   ` quic_llindhol
2022-02-02 18:06     ` Michael D Kinney
2022-02-07 11:46 ` Leif Lindholm [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-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=YgEGj/IAhpbg9izl@leviathan \
    --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