From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master
Date: Fri, 10 Jan 2020 11:51:53 +0100 [thread overview]
Message-ID: <fbdd5977-f885-5089-69f0-59d3e754f252@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9E5A184@ORSMSX113.amr.corp.intel.com>
On 01/09/20 22:37, Michael D Kinney wrote:
> Yes. That request is already captured in the BZ.
My bad -- I ran into the issue last night again, but had forgotten about
the BZ's particulars by then. Apologies!
Thanks
Laszlo
>> -----Original Message-----
>> From: Laszlo Ersek <lersek@redhat.com>
>> Sent: Thursday, January 9, 2020 1:31 PM
>> To: Kinney, Michael D <michael.d.kinney@intel.com>;
>> devel@edk2.groups.io; Sean Brogan
>> <sean.brogan@microsoft.com>; Bret Barkelew
>> <Bret.Barkelew@microsoft.com>; Gao, Liming
>> <liming.gao@intel.com>
>> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
>> CI is now active on edk2/master
>>
>> Hi Mike,
>>
>> On 01/06/20 19:17, Kinney, Michael D wrote:
>>> Laszlo,
>>>
>>> Sorry for the delay in getting to these
>> PactchCheck.py updates.
>>> I know it is frustrating to be blocked by these types
>> of issues.
>>> I try to look at 2406 tomorrow. I think the manual
>> override is
>>> potentially more complex to implement than the
>> requested changed
>>> to PatchCheck.py.
>>
>> can we please downgrade the commit message width check
>> from "error" to
>> "warning"?
>>
>> It is crucial that I be able to quote edk2 *source
>> code* in some commit
>> messages. And edk2 uses very long lines in C source
>> code.
>>
>> Thanks
>> Laszlo
>
>
>
>
next prev parent reply other threads:[~2020-01-10 10:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 2:55 EDK II Maintainers - EDK II CI is now active on edk2/master Michael D Kinney
2019-11-12 8:56 ` [edk2-devel] " Laszlo Ersek
2019-11-12 19:50 ` Michael D Kinney
2019-11-12 19:52 ` Michael D Kinney
2019-11-13 7:56 ` Laszlo Ersek
2019-11-13 8:57 ` Laszlo Ersek
2019-11-13 16:23 ` Michael D Kinney
2019-11-13 17:03 ` Laszlo Ersek
2019-11-26 8:23 ` Laszlo Ersek
2019-11-27 19:03 ` Michael D Kinney
2019-11-28 12:00 ` Laszlo Ersek
2019-12-02 19:55 ` Michael D Kinney
2019-12-03 8:56 ` Laszlo Ersek
2019-12-03 17:07 ` Michael D Kinney
2019-12-03 20:39 ` Laszlo Ersek
2019-12-06 11:02 ` Laszlo Ersek
2019-12-06 11:07 ` Laszlo Ersek
2020-01-02 14:42 ` Philippe Mathieu-Daudé
2020-01-02 18:36 ` Michael D Kinney
2020-01-06 14:58 ` Philippe Mathieu-Daudé
2020-01-03 13:29 ` Laszlo Ersek
2020-01-06 17:29 ` Laszlo Ersek
2020-01-06 18:17 ` Michael D Kinney
2020-01-07 9:00 ` Laszlo Ersek
2020-01-09 21:30 ` Laszlo Ersek
2020-01-09 21:37 ` Michael D Kinney
2020-01-10 10:51 ` Laszlo Ersek [this message]
2020-03-08 11:12 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2020-03-08 19:21 Sean
2020-03-08 19:53 ` Michael D Kinney
2020-03-09 19:29 ` Laszlo Ersek
2020-03-09 19:32 ` Laszlo Ersek
2020-03-09 22:00 ` Michael D Kinney
2020-03-09 19:37 ` Laszlo Ersek
2020-03-09 20:06 ` Laszlo Ersek
2020-03-09 21:44 ` Michael D Kinney
2020-03-10 7:53 ` 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=fbdd5977-f885-5089-69f0-59d3e754f252@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