From: Pavel Machek <pavel@ucw.cz>
To: Joe Perches <joe@perches.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 4.19
Date: Fri, 26 Oct 2018 10:51:58 +0200 [thread overview]
Message-ID: <20181026085158.GA20200@amd> (raw)
In-Reply-To: <7c258019d4746325ac323bd6d49746ab3ea84066.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
On Mon 2018-10-22 00:38:43, Joe Perches wrote:
> On Mon, 2018-10-22 at 08:32 +0100, Greg KH wrote:
>
> > Greg Kroah-Hartman (7):
> > Code of Conduct Interpretation: Add document explaining how the Code of Conduct is to be interpreted
> > Code of Conduct Interpretation: Properly reference the TAB correctly
> > Code of Conduct: Provide links between the two documents
> > Code of Conduct Interpretation: Put in the proper URL for the committee
> > Code of Conduct: Change the contact email address
> > MAINTAINERS: Add an entry for the code of conduct
>
> Regardless of the number of acks that were given
> to this patchset, I believe this was patch block
> was not done in a public manner and so should not
> have been applied within the single day after its
> initial publication.
I was wondering if I somehow missed the discussion.
No, this is not right :-(.
Based on this, no, I don't think Greg should be MAINTAINER of the code
of conduct.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-10-26 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 7:32 Linux 4.19 Greg KH
2018-10-22 7:38 ` Joe Perches
2018-10-26 8:51 ` Pavel Machek [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-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=20181026085158.GA20200@amd \
--to=pavel@ucw.cz \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.