From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "rfc@edk2.groups.io" <rfc@edk2.groups.io>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
Pedro Falcato <pedro.falcato@gmail.com>,
Leif Lindholm <leif@nuviainc.com>,
"Andrew Fish (afish@apple.com)" <afish@apple.com>
Subject: Re: [edk2-rfc] [edk2-devel] Proposal to switch TianoCore Code Review from email to GitHub Pull Requests on 5-24-2024
Date: Mon, 6 May 2024 18:09:00 +0200 [thread overview]
Message-ID: <CAMj1kXHgXQtVvoL5mCuOXn8ukF8-ycqvTSEBmO+AxxRC+rpA1Q@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB4929F7D046583A729D13EEF0D21C2@CO1PR11MB4929.namprd11.prod.outlook.com>
On Mon, 6 May 2024 at 17:57, Kinney, Michael D
<michael.d.kinney@intel.com> wrote:
>
> Hi Ard,
>
> Thais is an attribute of Mergify. I do not see a way to change that
> behavior.
>
> I do not know if using the GitHub merge capability or other merge services
> provides different behavior here or not.
>
> This specific request is not related to the change to GitHub PRs
> for code review. There is no intention to change the requirement
> for a maintainer to set the 'push' label and no intention to change
> away from Mergify at this time.
>
> Perhaps we can open your request as an independent request that we
> can find an owner to evaluate options and provide recommendations.
>
Yep that works for me - it is not an urgent issue anyway, just
something I realized while going through the thread.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118603): https://edk2.groups.io/g/devel/message/118603
Mute This Topic: https://groups.io/mt/105873467/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-05-06 16:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 17:43 [edk2-devel] Proposal to switch TianoCore Code Review from email to GitHub Pull Requests on 5-24-2024 Michael D Kinney
2024-05-01 18:12 ` Leif Lindholm
2024-05-01 23:19 ` Dionna Glaze via groups.io
2024-05-02 15:59 ` Brian J. Johnson
2024-05-02 16:09 ` Dionna Glaze via groups.io
2024-05-02 16:30 ` [edk2-rfc] " Michael D Kinney
2024-05-06 16:41 ` Leara, William via groups.io
2024-05-02 1:28 ` Rebecca Cran
2024-05-02 10:21 ` Leif Lindholm
2024-05-02 3:08 ` Michael Kubacki
2024-05-02 10:57 ` Leif Lindholm
2024-05-02 16:37 ` Michael D Kinney
2024-05-03 16:58 ` Michael Kubacki
2024-05-03 16:54 ` Michael Kubacki
2024-05-02 6:33 ` Marcin Juszkiewicz
2024-05-02 10:34 ` Leif Lindholm
2024-05-02 15:21 ` Michael Kubacki
2024-05-02 16:24 ` Michael D Kinney
2024-05-03 17:21 ` Michael Kubacki
2024-05-03 19:16 ` [edk2-rfc] " Michael D Kinney
2024-05-02 9:37 ` Ard Biesheuvel
2024-05-02 15:14 ` Michael Kubacki
2024-05-03 0:35 ` [edk2-rfc] " Rebecca Cran
2024-05-02 17:50 ` Pedro Falcato
2024-05-02 18:17 ` [edk2-rfc] " Michael D Kinney
2024-05-03 17:38 ` Pedro Falcato
2024-05-03 20:12 ` Michael D Kinney
2024-05-03 20:38 ` Michael D Kinney
2024-05-04 0:57 ` Michael Kubacki
2024-05-05 18:10 ` Pedro Falcato
2024-05-06 10:00 ` Ard Biesheuvel
2024-05-06 15:11 ` Michael D Kinney
2024-05-06 15:30 ` Ard Biesheuvel
2024-05-06 15:56 ` Michael D Kinney
2024-05-06 16:09 ` Ard Biesheuvel [this message]
2024-05-10 20:57 ` Brian J. Johnson
2024-05-15 17:03 ` Michael D Kinney
2024-05-24 12:20 ` [edk2-devel] [edk2-rfc] " Rebecca Cran
2024-05-24 14:53 ` Michael Kubacki
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=CAMj1kXHgXQtVvoL5mCuOXn8ukF8-ycqvTSEBmO+AxxRC+rpA1Q@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