From: zhanghailiang <zhanghailiang@xfusion.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Wen Congyang <wencongyang2@huawei.com>,
Gonglei <arei.gonglei@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"quintela@redhat.com" <quintela@redhat.com>,
"dgilbert@redhat.com" <dgilbert@redhat.com>
Subject: RE: [PATCH v2] MAINTAINERS: Change my email address
Date: Tue, 14 Dec 2021 12:38:41 +0000 [thread overview]
Message-ID: <1bde4be9d4664b0295e6e18a9e861529@xfusion.com> (raw)
In-Reply-To: <b96112c8-c279-5cec-8670-25f12b560f5b@redhat.com>
> -----Original Message-----
> From: Philippe Mathieu-Daudé <philmd@redhat.com>
> Sent: Tuesday, December 14, 2021 6:18 PM
> To: Daniel P. Berrangé <berrange@redhat.com>
> Cc: zhanghailiang <zhanghailiang@xfusion.com>; qemu-devel@nongnu.org;
> Gonglei <arei.gonglei@huawei.com>; Wen Congyang
> <wencongyang2@huawei.com>; dgilbert@redhat.com; quintela@redhat.com
> Subject: Re: [PATCH v2] MAINTAINERS: Change my email address
>
> On 12/14/21 10:22, Daniel P. Berrangé wrote:
> > On Tue, Dec 14, 2021 at 10:04:03AM +0100, Philippe Mathieu-Daudé wrote:
> >> On 12/14/21 08:54, Hailiang Zhang wrote:
> >>> The zhang.zhanghailiang@huawei.com email address has been stopped.
> >>> Change it to my new email address.
> >>>
> >>> Signed-off-by: Hailiang Zhang <zhanghailiang@xfusion.com>
> >>> ---
> >>> hi Juan & Dave,
> >>>
> >>> Firstly, thank you for your working on maintaining the COLO framework.
> >>> I didn't have much time on it in the past days.
> >>>
> >>> I may have some time in the next days since my job has changed.
> >>>
> >>> Because of my old email being stopped, i can not use it to send this patch.
> >>> Please help me to merge this patch.
> >>
> >> Can we have an Ack-by from someone working at Huawei?
> >
> > Why do we need that ?
>
> To avoid anyone impersonating Hailiang Zhang...
>
Agreed. This check is necessary. I totally understand.
> But it doesn't have to be from the same company, as long as someone knowing
> him vouch the change. Anyhow I am not nacking this patch, I am trying to have a
> safer process.
>
> > Subsystems are not owned by companies.
> >
> > If someone moves company and wants to carry on in their existing role
> > as maintainer that is fine and doesn't need approva from their old
> > company IMHO.
>
> I agree, this is why it is better to send that kind of change from the
> to-be-stopped email address while it is still valid.
>
I should send this patch before my old email address stopped, but I didn't get permission of
Sending email in new company until now. ☹
Thanks.
> Thanks,
>
> Phil.
next prev parent reply other threads:[~2021-12-14 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 7:54 [PATCH v2] MAINTAINERS: Change my email address Hailiang Zhang
2021-12-14 9:04 ` Philippe Mathieu-Daudé
2021-12-14 9:13 ` zhanghailiang
2021-12-14 9:22 ` Daniel P. Berrangé
2021-12-14 10:08 ` Juan Quintela
2021-12-14 10:15 ` Gonglei (Arei) via
2021-12-14 10:19 ` Philippe Mathieu-Daudé
2021-12-14 10:18 ` Philippe Mathieu-Daudé
2021-12-14 12:38 ` zhanghailiang [this message]
2021-12-16 1:49 ` Zhang, Chen
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=1bde4be9d4664b0295e6e18a9e861529@xfusion.com \
--to=zhanghailiang@xfusion.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=wencongyang2@huawei.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;
as well as URLs for NNTP newsgroup(s).