From: stephano <stephano.cetola@linux.intel.com>
To: edk2-devel@lists.01.org
Subject: Re: [edk2-announce] March Community Meeting Minutes
Date: Mon, 11 Mar 2019 15:29:34 -0700 [thread overview]
Message-ID: <9307e691-21a3-bb58-0d30-2a4add7cac4a@linux.intel.com> (raw)
In-Reply-To: <bfd246e1-ed04-90f7-4f12-a06630bca119@linux.intel.com>
On 3/11/2019 9:33 AM, stephano wrote:
> Stephano has taken an action item to work with the Kubernetes community
> to see what trade-offs and benefits they experience using GitHub.
I realized earlier today that rust-lang also uses GitHub style pull
requests:
https://github.com/rust-lang/rust/pulls
Since they certainly qualify as a popular open source project I'll add
them to my list of communities to contact. :)
Cheers,
Stephano
prev parent reply other threads:[~2019-03-11 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 16:33 [edk2-announce] March Community Meeting Minutes stephano
2019-03-11 20:55 ` Rebecca Cran
2019-03-11 22:20 ` stephano
2019-03-11 22:54 ` Rebecca Cran
2019-03-11 22:29 ` stephano [this message]
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=9307e691-21a3-bb58-0d30-2a4add7cac4a@linux.intel.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