From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: philmd@oss.qualcomm.com, qemu-devel@nongnu.org
Subject: Re: [philmd@linaro.org: Your email to Phil Mathieu-Daude Re: [PATCH] docs: outline some guidelines for security classification]
Date: Tue, 7 Jul 2026 14:58:01 +0100 [thread overview]
Message-ID: <ak0F6avwblY42d_O@redhat.com> (raw)
In-Reply-To: <20260707095144-mutt-send-email-mst@kernel.org>
On Tue, Jul 07, 2026 at 09:52:13AM -0400, Michael S. Tsirkin wrote:
> Maybe we can merge a mailmap entry so get_maintainer DTRT? Thanks!
This case was my fault for cut & pasting his address from an outdated
source, rather than get_maintainer.
> ----- Forwarded message from Philippe Mathieu-Daudé <philmd@linaro.org> -----
>
> From: Philippe Mathieu-Daudé <philmd@linaro.org>
> Date: Tue, 7 Jul 2026 06:43:21 -0700
> To: mst@redhat.com
> Subject: Your email to Phil Mathieu-Daude Re: [PATCH] docs: outline some guidelines for security classification
> Message-ID: <CAPMQPEJDi9d_mTpvfsYRJRLmBxkthBMPF_XV3n7_q2nonHxzvQ@mail.gmail.com>
>
> Thank you for your email.
>
> Phil Mathieu-Daude no longer works for Linaro.
>
> If your email is related to Linaro business, please use the Contact
> form (https://www.linaro.org/contact/) if you do not have another
> Linaro email address to use.
>
> Thank you.
>
> ----- End forwarded message -----
>
>
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-07-07 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 13:52 [philmd@linaro.org: Your email to Phil Mathieu-Daude Re: [PATCH] docs: outline some guidelines for security classification] Michael S. Tsirkin
2026-07-07 13:58 ` Daniel P. Berrangé [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-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=ak0F6avwblY42d_O@redhat.com \
--to=berrange@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@oss.qualcomm.com \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.