From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <greg@kroah.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [GIT PULL] code of conduct fixes for 4.19-rc8
Date: Mon, 22 Oct 2018 23:10:40 -0700 [thread overview]
Message-ID: <a401f973508662fa241b1410e08480884baca606.camel@perches.com> (raw)
In-Reply-To: <800b68eb-9cf4-9c72-104d-0d4d9ae26ea1@infradead.org>
On Mon, 2018-10-22 at 23:05 -0700, Randy Dunlap wrote:
> On 10/22/18 9:16 PM, Joe Perches wrote:
> > As James Bottomley has suggested multiple times,
> > I'd much rather kernel development use the debian
> > code of conduct verbatim than even this modified one.
> >
> > https://www.debian.org/code_of_conduct
>
> Yes, that and the Samba URL are good.
>
> And it's disappointing how patches from James are acked or reviewed on the
> mailing lists and then mostly ignored (until the maintainer summit) while
> other patches are merged into the mainline git tree.
>
> It seems to be very one-sided.
Perhaps an apt description is 'cabal like'.
next prev parent reply other threads:[~2018-10-23 6:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 20:15 [GIT PULL] code of conduct fixes for 4.19-rc8 James Bottomley
2018-10-22 21:10 ` Greg Kroah-Hartman
2018-10-23 4:16 ` [Ksummit-discuss] " Joe Perches
2018-10-23 6:05 ` Randy Dunlap
2018-10-23 6:10 ` Joe Perches [this message]
2018-10-23 7:07 ` Josh Triplett
2018-10-23 9:01 ` Mark Brown
2018-10-23 9:09 ` James Bottomley
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=a401f973508662fa241b1410e08480884baca606.camel@perches.com \
--to=joe@perches.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).