From: Aaron Conole <aconole@redhat.com>
To: Michael Santana <msantana@redhat.com>
Cc: dev@dpdk.org, Michael Santana <maicolgabriel@hotmail.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] Change email in maintainers file
Date: Mon, 19 Aug 2019 08:28:49 -0400 [thread overview]
Message-ID: <f7t5zmtfif2.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <20190815225452.16410-1-msantana@redhat.com> (Michael Santana's message of "Thu, 15 Aug 2019 18:54:52 -0400")
Michael Santana <msantana@redhat.com> writes:
> Change email address for Michael Santana to personal email in the
> MAINTAINERS file
>
> Signed-off-by: Michael Santana <msantana@redhat.com>
> Signed-off-by: Michael Santana <maicolgabriel@hotmail.com>
> ---
>
> NOTE: My internship at Red Hat is ending soon so I will not be able
> to monitor my red hat email. I will not monitor the mailing list
> as much, so CI patches should go primarily to Aaron Carole.
:'(
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2019-08-19 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 22:54 Michael Santana
2019-08-19 12:28 ` Aaron Conole [this message]
2019-09-09 20:46 ` Thomas Monjalon
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=f7t5zmtfif2.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=msantana@redhat.com \
--cc=thomas@monjalon.net \
/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).