From: "Cédric Le Goater" <clg@kaod.org>
To: Andrew Jeffery <andrew@codeconstruct.com.au>, andrew@aj.id.au
Cc: joel@jms.id.au, peter.maydell@linaro.org, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, qemu-trivial@nongnu.org,
Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: aspeed: Update Andrew's email address
Date: Tue, 24 Oct 2023 11:36:59 +0200 [thread overview]
Message-ID: <aaa71ccc-e7d4-46f4-b902-22a422ff895a@kaod.org> (raw)
In-Reply-To: <20230925062212.66112-1-andrew@codeconstruct.com.au>
On 9/25/23 08:22, Andrew Jeffery wrote:
> I've changed employers, have company email that deals with patch-based
> workflows without too much of a headache, and am trying to steer some
> content out of my personal mail.
>
> Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
> ---
>
> Hi Cédric, do you mind including this in your Aspeed queue?
I am not sure to send an Aspeed PR. May be this change could go
through qemu-trivial ?
Thanks,
C.
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 355b1960ce46..b142c09628b9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1108,7 +1108,7 @@ F: docs/system/arm/emcraft-sf2.rst
> ASPEED BMCs
> M: Cédric Le Goater <clg@kaod.org>
> M: Peter Maydell <peter.maydell@linaro.org>
> -R: Andrew Jeffery <andrew@aj.id.au>
> +R: Andrew Jeffery <andrew@codeconstruct.com.au>
> R: Joel Stanley <joel@jms.id.au>
> L: qemu-arm@nongnu.org
> S: Maintained
next prev parent reply other threads:[~2023-10-24 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 6:22 [PATCH] MAINTAINERS: aspeed: Update Andrew's email address Andrew Jeffery
2023-09-25 7:58 ` Cédric Le Goater
2023-09-25 8:00 ` Andrew Jeffery
2023-10-24 9:36 ` Cédric Le Goater [this message]
2023-10-25 8:57 ` Cédric Le Goater
2023-10-26 5:18 ` Andrew Jeffery
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=aaa71ccc-e7d4-46f4-b902-22a422ff895a@kaod.org \
--to=clg@kaod.org \
--cc=andrew@aj.id.au \
--cc=andrew@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 NNTP newsgroup(s).