From: stephano <stephano.cetola@linux.intel.com>
To: edk2-devel@lists.01.org
Subject: Re: [edk2-announce] Community Meeting Minutes
Date: Tue, 19 Feb 2019 22:45:29 -0800 [thread overview]
Message-ID: <e26cee61-472c-0755-c467-cc800b0db4fe@linux.intel.com> (raw)
In-Reply-To: <6b070757-61b6-c41e-bfd6-aff48a7bf62b@linux.intel.com>
On 2/19/2019 10:23 PM, stephano wrote:
>
> Groups.io
> ---------------------
> Laszlo and I will evaluate Groups.io, however initial impressions is
> that this will work as a communication platform going forward. We'd like
> to use this for design discussions and as a replacement for our current
> mailing list as 01.org does not allow attachments or whistling.
I have double checked, and indeed, 01.org does not allow whistling of
any kind. Thank you autocorrect for that insightful suggestion.
I would like to note that 01.org also does not allow white-listing,
something perhaps more valuable to our community.
Kind Regards,
Stephano
next prev parent reply other threads:[~2019-02-20 6:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 6:23 [edk2-announce] Community Meeting Minutes stephano
2019-02-20 6:45 ` stephano [this message]
2019-02-20 7:49 ` Rebecca Cran
-- strict thread matches above, loose matches on Subject: below --
2019-01-11 19:26 stephano
2019-01-13 3:59 ` Rebecca Cran
2019-01-14 9:28 ` Laszlo Ersek
2019-01-14 17:06 ` stephano
2019-02-07 17:52 ` Jeremiah Cox
2019-02-07 18:30 ` stephano
2019-02-08 6:41 ` Rebecca Cran
2019-02-08 9:01 ` Laszlo Ersek
2019-02-08 17:33 ` Rebecca Cran
2019-02-08 17:52 ` Andrew Fish
2019-02-22 11:52 ` Rebecca Cran
2019-02-08 20:33 ` Laszlo Ersek
2019-02-08 13:58 ` Ard Biesheuvel
2019-02-14 19:07 ` Jeremiah Cox
2019-02-14 20:27 ` Rebecca Cran
2019-02-14 22:13 ` Kinney, Michael D
2019-02-15 2:56 ` Rebecca Cran
2019-02-15 14:30 ` Laszlo Ersek
2019-02-15 17:55 ` stephano
2019-02-15 8:43 ` Ard Biesheuvel
2019-02-15 14:23 ` Laszlo Ersek
2019-02-15 19:54 ` Felix Polyudov
2019-02-15 22: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=e26cee61-472c-0755-c467-cc800b0db4fe@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