From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH v3 3/6] ArmVirtPkg: Fix build failure due to Tftp library removal
Date: Wed, 29 Nov 2017 10:05:09 +0000 [thread overview]
Message-ID: <CAKv+Gu-B6get=NcS2z_7SF=yug3TNSAHpKkYQMwY1OZOSidCGA@mail.gmail.com> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5BAD6BE0@SHSMSX104.ccr.corp.intel.com>
On 29 November 2017 at 10:03, Ni, Ruiyu <ruiyu.ni@intel.com> wrote:
> I see. Thanks.
> I will revise the commit message and send out in V4.
>
> BTW, which mail client are you using?
I use the Gmail web interface.
> All mails from lists.01.org are flatly shown in my Outlook, which is very hard
> to track.
>
Yes, it helps if you use a mail client that keeps the messages together.
--
Ard.
next prev parent reply other threads:[~2017-11-29 10:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 0:59 [PATCH v3 0/6] Fix build failure due to tftp/dp library removal Ruiyu Ni
2017-11-29 0:59 ` [PATCH v3 1/6] ShellPkg/tftp: Correct file comments header of Tftp.uni Ruiyu Ni
2017-11-29 0:59 ` [PATCH v3 2/6] EmulatorPkg: Fix build failure due to Tftp library removal Ruiyu Ni
2017-11-29 0:59 ` [PATCH v3 3/6] ArmVirtPkg: " Ruiyu Ni
2017-11-29 9:36 ` Ni, Ruiyu
2017-11-29 9:44 ` Ard Biesheuvel
2017-11-29 9:57 ` Ni, Ruiyu
2017-11-29 9:59 ` Ard Biesheuvel
2017-11-29 10:03 ` Ni, Ruiyu
2017-11-29 10:05 ` Ard Biesheuvel [this message]
2017-11-29 11:06 ` Laszlo Ersek
2017-11-29 0:59 ` [PATCH v3 4/6] BeagleBoardPkg: " Ruiyu Ni
2017-11-29 7:57 ` Ard Biesheuvel
2017-11-29 8:28 ` Ni, Ruiyu
2017-11-29 8:40 ` Ard Biesheuvel
2017-11-29 0:59 ` [PATCH v3 5/6] CorebootPayloadPkg: Fix build failure due to Tftp/Dp " Ruiyu Ni
2017-11-29 1:51 ` You, Benjamin
2017-11-29 0:59 ` [PATCH v3 6/6] OvmfPkg: Add tftp dynamic command Ruiyu Ni
2017-11-29 10:53 ` Laszlo Ersek
2017-11-29 13:12 ` Ni, Ruiyu
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='CAKv+Gu-B6get=NcS2z_7SF=yug3TNSAHpKkYQMwY1OZOSidCGA@mail.gmail.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