From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Kristen Carlson Accardi <kristen@linux.intel.com>,
linux-doc@vger.kernel.org, corbet@lwn.net,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices
Date: Tue, 27 Sep 2022 10:22:00 +0200 [thread overview]
Message-ID: <YzKyqNJk72TY//42@kroah.com> (raw)
In-Reply-To: <dd89a30e-5403-8844-036c-9c9107cac888@gmail.com>
On Tue, Sep 27, 2022 at 03:19:29PM +0700, Bagas Sanjaya wrote:
> On 9/27/22 04:11, Kristen Carlson Accardi wrote:
> > The Code of Conduct interpretation does not reflect the current
> > practices of the CoC committee or the TAB. Update the documentation
> > to remove references to initial committees and boot strap periods
> > since it is past that time, and note that the this document
> > does serve as the documentation for the CoC committee processes.
> >
>
> When was the bootstrap period be concluded?
I do not understand the question, sorry. What exactly are you asking
here?
confused,
greg k-h
next prev parent reply other threads:[~2022-09-27 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 21:11 [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices Kristen Carlson Accardi
2022-09-26 23:12 ` Jonathan Corbet
2022-09-27 15:59 ` Kristen Carlson Accardi
2022-09-27 16:03 ` Jonathan Corbet
2022-09-27 8:19 ` Bagas Sanjaya
2022-09-27 8:22 ` Greg Kroah-Hartman [this message]
2022-09-27 8:27 ` Bagas Sanjaya
2022-09-27 8:43 ` Greg Kroah-Hartman
2022-09-27 12:08 ` Bagas Sanjaya
2022-09-27 8:30 ` Bagas Sanjaya
2022-09-29 19:15 ` Jonathan Corbet
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=YzKyqNJk72TY//42@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=kristen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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.