From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io, rebecca@bsdio.com,
Chris Fernald <chris.fernald@outlook.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] Contribution process for containers repo?
Date: Tue, 28 Mar 2023 10:24:24 -0400 [thread overview]
Message-ID: <54d8ee81-8ac6-0a88-448c-c00ffe86da36@linux.microsoft.com> (raw)
In-Reply-To: <efeb5b01-e194-23bd-3510-efd2eaefc1c7@bsdio.com>
Hi Rebecca,
I've seen pull requests used and I don't recall patches being sent to
the mailing list.
A change may need integration work in the edk2 repo and, of course, a
patch is sent to the list for that.
Thanks,
Michael
On 3/28/2023 6:35 AM, Rebecca Cran wrote:
> The CONTRIBUTING.md file in https://github.com/tianocore/containers says
> that GitHub Pull Requests are used for contributions.
>
> I was wondering if that's correct, or if patches should be sent to this
> mailing list instead (or in addition)?
>
>
> Thanks.
>
> Rebecca Cran
>
>
>
>
>
next prev parent reply other threads:[~2023-03-28 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 10:35 Contribution process for containers repo? Rebecca Cran
2023-03-28 14:24 ` Michael Kubacki [this message]
2023-03-28 15:19 ` [edk2-devel] " Rebecca Cran
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=54d8ee81-8ac6-0a88-448c-c00ffe86da36@linux.microsoft.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