From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Linux 4.19-rc4 released, an apology, and a maintainership note
Date: Mon, 17 Sep 2018 10:09:58 -0700 [thread overview]
Message-ID: <5e67ac14892b711294ca91b05c699627ea2adf09.camel@perches.com> (raw)
In-Reply-To: <CA+55aFy+Hv9O5citAawS+mVZO+ywCKd9NQ2wxUmGsz9ZJzqgJQ@mail.gmail.com>
On Sun, 2018-09-16 at 12:22 -0700, Linus Torvalds wrote:
> Greg Kroah-Hartman (1):
> Code of Conduct: Let's revamp it.
I believe it would be better if this sort of change
had on-list and public discussion before being applied.
next prev parent reply other threads:[~2018-09-17 17:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 19:22 Linux 4.19-rc4 released, an apology, and a maintainership note Linus Torvalds
2018-09-16 21:42 ` [...] " Adam Borowski
2018-09-16 23:59 ` Moritz Obermeier
2018-09-17 0:18 ` Linux 4.19-rc4 released, " Rene Herman
2018-09-17 0:20 ` [...] " Andy Isaacson
2018-09-17 0:23 ` Linux 4.19-rc4 released, " Rene Herman
2018-09-17 6:57 ` opal hart
2018-09-17 7:57 ` […] " Martin Steigerwald
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-17 12:58 ` Guenter Roeck
2018-09-17 17:09 ` Joe Perches [this message]
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
2018-09-17 2:15 Luke Kenneth Casson Leighton
2018-09-18 2:10 ` Luke Kenneth Casson Leighton
2018-09-30 11:47 ` Luke Kenneth Casson Leighton
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=5e67ac14892b711294ca91b05c699627ea2adf09.camel@perches.com \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.org \
--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 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).