From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: yuchenlin <yuchenlin@synology.com>,
Anthony Perard <anthony.perard@citrix.com>,
Jordan Justen <jordan.l.justen@intel.com>,
edk2-devel-01 <edk2-devel@lists.01.org>,
Phil Dennis-Jordan <phil@philjordan.eu>
Subject: Re: [PATCH v2 5/5] OvmfPkg: simply use the Bochs interface for vmsvga
Date: Mon, 12 Nov 2018 13:21:44 +0100 [thread overview]
Message-ID: <97ebc87a-1266-0f18-8f99-13b67f90374f@redhat.com> (raw)
In-Reply-To: <CAP+75-WC3t7b+=gX=HzbSSbxN3T+nHDAo0+vo5sKCC268zc-2g@mail.gmail.com>
On 11/12/18 12:28, Philippe Mathieu-Daudé wrote:
> On Mon, Nov 12, 2018 at 12:20 PM Laszlo Ersek <lersek@redhat.com>
> wrote:
>> On 11/06/18 14:44, Philippe Mathieu-Daudé wrote:
>>> On 6/11/18 14:36, Laszlo Ersek wrote:
>>>> On 11/06/18 12:47, Laszlo Ersek wrote:
>>>>
>>>>> ... While we discuss this, I'll go ahead and push the first four
>>>>> patches. The code being reverted is dead anyway. I'll report back
>>>>> about the commit hashes.
>>>>
>>>> Before pushing the first four patches, I regression-tested them as
>>>> well.
>>>> Using: Cirrus, stdvga, and QXL. My QEMU version was
>>>> v3.0.0-1763-gb2f7a038bb4c. The machine type was "pc-q35-3.0".
>>>>
>>>> For the first four patches:
>>>> - Regression-tested-by: Laszlo Ersek <lersek@redhat.com>,
>>>> - pushed them as commit range 62ea70e31285..328409ce8de7.
>>>
>>> Thanks Laszlo!
>>> A bit late, but 1-4 reviewed too.
>>
>> can you please formally state your R-b, for the first four patches?
>> For when I apply them again, after edk2-stable201811.
>
> Sure, I was not aware the "reply to cover" option was not formal for
> this list, I'll do.
> (TIL: "reply to cover" is list CoC specific)
"reply to cover letter" is perfectly fine on this list as well (it never
occurred to me that it would be unacceptable for any list in the first
place) -- but where did you respond to:
[edk2] [PATCH v2 0/5] OvmfPkg: simply use the Bochs interface for vmsvga
http://mid.mail-archive.com/20181102032402.19686-1-yuchenlin@synology.com
?
... Ahhh, wait, now I see where our misunderstanding is. :) By
"formally", I did not mean that you should respond to every single patch
(#1 through #4) separately, with your R-b. Responding under the cover
letter, or even just in this thread, is perfectly fine. What I'm asking
for instead is that you please "formally" spell out your Reviewed-by
tag. In edk2 we strongly prefer carrying R-b tags from the mailing list
to commit messages verbatim (i.e. with the clipboard). We dislike
synthesizing formal R-b tags from messages like "sure, reviewed by me
too".
So, again, in this context, "formally" only means that you please repeat
your "reviewed too" message "formally" with an R-b tag, spelled out. A
response in this thread is perfectly fine.
Sorry about the confusion!
Laszlo
next prev parent reply other threads:[~2018-11-12 12:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 3:23 [PATCH v2 0/5] OvmfPkg: simply use the Bochs interface for vmsvga yuchenlin
2018-11-02 3:23 ` [PATCH v2 1/5] Revert "OvmfPkg/QemuVideoDxe: list "UnalignedIoInternal.h" in the INF file" yuchenlin
2018-11-06 10:03 ` Laszlo Ersek
2018-11-02 3:23 ` [PATCH v2 2/5] Revert "OvmfPkg/QemuVideoDxe: VMWare SVGA device support" yuchenlin
2018-11-06 10:36 ` Laszlo Ersek
2018-11-02 3:24 ` [PATCH v2 3/5] Revert "OvmfPkg/QemuVideoDxe: Helper functions for unaligned port I/O." yuchenlin
2018-11-06 10:44 ` Laszlo Ersek
2018-11-02 3:24 ` [PATCH v2 4/5] Revert "OvmfPkg: VMWare SVGA display device register definitions" yuchenlin
2018-11-06 10:48 ` Laszlo Ersek
2018-11-02 3:24 ` [PATCH v2 5/5] OvmfPkg: simply use the Bochs interface for vmsvga yuchenlin
2018-11-06 11:47 ` Laszlo Ersek
2018-11-06 13:36 ` Laszlo Ersek
2018-11-06 13:44 ` Philippe Mathieu-Daudé
2018-11-06 16:20 ` Laszlo Ersek
2018-11-07 2:37 ` yuchenlin
2018-11-12 11:19 ` Laszlo Ersek
2018-11-12 11:28 ` Philippe Mathieu-Daudé
2018-11-12 12:21 ` Laszlo Ersek [this message]
2018-11-07 2:36 ` yuchenlin
2018-11-05 22:52 ` [PATCH v2 0/5] " Laszlo Ersek
2018-11-12 14:16 ` Philippe Mathieu-Daudé
2018-11-12 15:40 ` Laszlo Ersek
2018-11-15 11:56 ` Laszlo Ersek
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=97ebc87a-1266-0f18-8f99-13b67f90374f@redhat.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