From: Patrick Williams <patrick@stwcx.xyz>
To: Joseph Reynolds <jrey@linux.ibm.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Security Working Group meeting - Wednesday August 17
Date: Wed, 17 Aug 2022 15:29:39 -0500 [thread overview]
Message-ID: <Yv1PsykUiUbKU3jm@heinlein.stwcx.org.github.beta.tailscale.net> (raw)
In-Reply-To: <c002db20-f047-b4aa-1137-a9cc96048706@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Wed, Aug 17, 2022 at 03:11:46PM -0500, Joseph Reynolds wrote:
> On 8/16/22 10:07 PM, Joseph Reynolds wrote:
> 4 SELinux design. Request for re-review.
> https://gerrit.openbmc.org/c/openbmc/docs/+/53205
> <https://gerrit.openbmc.org/c/openbmc/docs/+/53205>
>
> Advice on how to create interest in re-reviewing a design. Use Discord:
> Ping specific reviewers and ask specific questions about design issues,
> if it is solved; ask if the design can be approved.
Step 1. Do not disappear for months at a time, without responding to
any feedback, and then expect reviewers to drop everything when you
decide it is time to show up again.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-17 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 3:07 Security Working Group meeting - Wednesday August 17 Joseph Reynolds
2022-08-17 5:11 ` Andrew Jeffery
2022-08-17 16:13 ` Joseph Reynolds
2022-08-17 16:57 ` Brad Bishop
2022-08-17 20:11 ` Joseph Reynolds
2022-08-17 20:26 ` Security Working Group meeting - moved to Discord Voice channel Joseph Reynolds
2023-08-28 19:56 ` Security Working Group meeting - regular meetings discontinued Joseph Reynolds
2022-08-17 20:29 ` Patrick Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-17 17:40 Security Working Group meeting - Wednesday August 17 Nick Rivers
2022-08-17 17:47 ` Brad Bishop
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-all 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=Yv1PsykUiUbKU3jm@heinlein.stwcx.org.github.beta.tailscale.net \
--to=patrick@stwcx.xyz \
--cc=jrey@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.