From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>,
"Zhang, Shenglei" <shenglei.zhang@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 1/3] Maintainers.txt: Remove EdkShellPkg and EkdShellBinPkg
Date: Mon, 5 Nov 2018 17:20:18 +0000 [thread overview]
Message-ID: <8128B8FD-4CAF-4055-94C0-D0D461AC7BBE@intel.com> (raw)
In-Reply-To: <e54b71f8-3561-3a03-5c37-18f3df107e4c@redhat.com>
Laszlo, thanks a bunch for this information. I hadn’t realized I had to do that manually.
Jaben
> On Nov 5, 2018, at 8:52 AM, Laszlo Ersek <lersek@redhat.com> wrote:
>
>> On 11/01/18 12:31, Leif Lindholm wrote:
>>> On Thu, Nov 01, 2018 at 06:03:22AM +0000, Zhang, Shenglei wrote:
>>> Hi Leif,
>>>
>>> Thanks for your comments. Actually there is a cover letter.
>>> https://lists.01.org/pipermail/edk2-devel/2018-October/031666.html
>>
>> Ah, I missed that one since I was on cc on the rest of the set, but
>> not the cover letter.
>
> Indeed it is important to collect all CC's from the individual patches
> and to add them to the cover letter.
>
> Laszlo
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-11-05 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 6:05 [PATCH 0/3] Remove EdkShellBinPkg and EdkShellPkg shenglei
2018-10-31 6:05 ` [PATCH 1/3] Maintainers.txt: Remove EdkShellPkg and EkdShellBinPkg shenglei
2018-10-31 9:08 ` Ni, Ruiyu
2018-10-31 11:01 ` Leif Lindholm
2018-11-01 6:03 ` Zhang, Shenglei
2018-11-01 11:31 ` Leif Lindholm
2018-11-05 16:52 ` Laszlo Ersek
2018-11-05 17:20 ` Carsey, Jaben [this message]
2018-10-31 6:05 ` [PATCH 2/3] EdkShellBinPkg: Remove EdkShellBinPkg shenglei
2018-10-31 6:05 ` [PATCH 3/3] EdkShellPkg: Remove EdkShellPkg shenglei
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=8128B8FD-4CAF-4055-94C0-D0D461AC7BBE@intel.com \
--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