All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	clm@fb.com, dan.j.williams@intel.com, corbet@lwn.net,
	olof@lxom.net, rostedt@goodmis.org,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Tue, 18 Sep 2018 03:10:35 +0100	[thread overview]
Message-ID: <CAPweEDxGEi-Nz1yMiLVW2FDm+iSqH_0SKOK6o4zO=KNaG2=XNw@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDwKzoxoVFSNbSnsHtqNhxB+AbdjD9XMXW0MEwNPGdr3Xg@mail.gmail.com>

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8a104f8b5867c682d994ffa7a74093c54469c11f

ahh, guys?  ah... i'm going to try *really* hard to follow the advice
that's listed here ok?
http://www.pndc.com/documents/_PDF%20Text-PNDC%20WORKS.pdf  it's a
little challenging to do so in email, as it's specifically designed
(page 6) for face-to-face conversations.

 following point (1) on page 6, i believe that the question i should
be asking is best phrased as follows:

 * what was the intent behind the change to a "code of conduct"?

 following point (4) on page 7, a second question i believe should be
phrased as follows:

 * whilst the "positive" list of behaviours look good on first glance,
we've witnessed what happened with freebsd when they adopted a "code
of conduct": would a (public) reasonable and rational discussion with
a view to removing the "proscribed" list of negative behaviours be
welcome? [1]

l.

[1] it's a little more complex than that, you get the general idea.

  reply	other threads:[~2018-09-18  2:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17  2:15 Linux 4.19-rc4 released, an apology, and a maintainership note Luke Kenneth Casson Leighton
2018-09-18  2:10 ` Luke Kenneth Casson Leighton [this message]
2018-09-30 11:47 ` Luke Kenneth Casson Leighton
  -- strict thread matches above, loose matches on Subject: below --
2018-09-17  8:53 […] " Martin Steigerwald
2018-09-30 12:09 ` Re: Linux 4.19-rc4 released, " lkcl
2018-09-30 14:07   ` Martin Steigerwald
2018-09-30 16:27     ` Luke Kenneth Casson Leighton
2018-09-16 19:22 Linus Torvalds
2018-09-17  0:18 ` Rene Herman
2018-09-17  0:23 ` Rene Herman
2018-09-17  6:57 ` opal hart
2018-09-17 12:58 ` Guenter Roeck
2018-09-17 17:09 ` Joe Perches
2018-09-17 21:09 ` Michael Woods
2018-09-18  1:30   ` Pavel Snajdr
2018-09-21 22:13     ` Michael Woods
2018-10-04 14:57     ` Eric W. Biederman
2018-10-08 15:29       ` Enrico Weigelt, metux IT consult
2018-10-08 13:54     ` Enrico Weigelt, metux IT consult
2018-10-08 16:36 ` Enrico Weigelt, metux IT consult

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='CAPweEDxGEi-Nz1yMiLVW2FDm+iSqH_0SKOK6o4zO=KNaG2=XNw@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --cc=clm@fb.com \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lxom.net \
    --cc=rostedt@goodmis.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.