public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io
Cc: michael.d.kinney@intel.com,
	"Sean Brogan" <sean.brogan@microsoft.com>,
	"Bret Barkelew" <Bret.Barkelew@microsoft.com>,
	"Gao, Liming" <liming.gao@intel.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master
Date: Fri, 6 Dec 2019 12:07:48 +0100	[thread overview]
Message-ID: <860d55eb-5ef8-0f66-a047-5614b3b7e9cd@redhat.com> (raw)
In-Reply-To: <836dd53e-b8ad-17c2-f94d-c1756e715f50@redhat.com>

On 12/06/19 12:02, Laszlo Ersek wrote:
> Hi Mike,
> 
> On 11/12/19 03:55, Michael D Kinney wrote:
>> EDK II Maintainers,
>>
>> EDK II CI Phase 1 feature is now active on edk2/master.
>>
>> Please use a GitHub pull request from a branch in a personal
>> fork of the edk2 repository with a 'push' label to request
>> a set of patches to be pushed to edk2/master.  The GitHub PR
>> replaces the 'git push' operation currently used to commit
>> changes to edk2/master.
>>
>> You will need to configure your notifications from the edk2
>> repository to make sure you receive email notifications
>> when the checks against the GitHub PR passes or fails.
>>
>> If you submit a GitHub Pull Request without the 'push'
>> label, then the CI checks are run and the results are
>> generated.
>>
>> Please let us know if there are any questions about this
>> change in the development process.
> 
> I don't know where I can file RFEs for the CI system.
> 
> For now, I've filed:
> 
> https://bugzilla.tianocore.org/show_bug.cgi?id=2406
> 
> The request is to allow subsystem maintainers to opt out of, or waive,
> PatchCheck.py failures. The commit message line length checks in
> PatchCheck.py make sense as a default, but there are valid cases when
> they should be turned off. Please see details in the BZ.

Forgot to CC Phil on this message, sorry about that; doing it now.
Laszlo


  reply	other threads:[~2019-12-06 11:07 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 [this message]
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
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=860d55eb-5ef8-0f66-a047-5614b3b7e9cd@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