public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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:43:29 +0200	[thread overview]
Message-ID: <YzK3sSrHSckm7T3b@kroah.com> (raw)
In-Reply-To: <f0c27a5b-fee2-eb64-6855-639e7ea65d37@gmail.com>

On Tue, Sep 27, 2022 at 03:27:24PM +0700, Bagas Sanjaya wrote:
> On 9/27/22 15:22, Greg Kroah-Hartman wrote:
> >> When was the bootstrap period be concluded?
> > 
> > I do not understand the question, sorry.  What exactly are you asking
> > here?
> > 
> > confused,
> > 
> > greg k-h
> 
> Hi Greg,
> 
> In the patch, the mention to bootstrap period of CoC committee is
> replaced with note about dynamic nature of CoC interpretation. I asked
> when the duration of bootstrap period was before we got into status quo.

It was a while ago, a few years perhaps?  We had forgotten to update the
document since then, sorry.

greg k-h

  reply	other threads:[~2022-09-27  8:43 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
2022-09-27  8:27     ` Bagas Sanjaya
2022-09-27  8:43       ` Greg Kroah-Hartman [this message]
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=YzK3sSrHSckm7T3b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox