From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Mishi Choudhary <mishi@linux.com>
Subject: [Ksummit-discuss] [PATCH 3/7] Code of Conduct Interpretation: Properly reference the TAB correctly
Date: Sat, 20 Oct 2018 15:50:21 +0200 [thread overview]
Message-ID: <20181020135021.GD32218@kroah.com> (raw)
In-Reply-To: <20181020134908.GA32218@kroah.com>
We use the term "TAB" before defining it later in the document. Fix
that up by defining it at the first location.
Reported-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Acked-by: Chris Mason <clm@fb.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Theodore Ts'o <tytso@mit.edu>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
.../process/code-of-conduct-interpretation.rst | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst
index b14441711f7b..ecf84cd29735 100644
--- a/Documentation/process/code-of-conduct-interpretation.rst
+++ b/Documentation/process/code-of-conduct-interpretation.rst
@@ -45,11 +45,11 @@ regarding conduct issues.
Maintainers should be willing to help when problems occur, and work with
others in the community when needed. Do not be afraid to reach out to
-the TAB or other maintainers if you're uncertain how to handle
-situations that come up. It will not be considered a violation report
-unless you want it to be. If you are uncertain about approaching the
-TAB or any other maintainers, please reach out to our conflict mediator,
-Mishi Choudhary <mishi@linux.com>.
+the Technical Advisory Board (TAB) or other maintainers if you're
+uncertain how to handle situations that come up. It will not be
+considered a violation report unless you want it to be. If you are
+uncertain about approaching the TAB or any other maintainers, please
+reach out to our conflict mediator, Mishi Choudhary <mishi@linux.com>.
In the end, "be kind to each other" is really what the end goal is for
everybody. We know everyone is human and we all fail at times, but the
@@ -125,9 +125,9 @@ are listed at <URL>. Members can not access reports made before they
joined or after they have left the committee.
The initial Code of Conduct Committee consists of volunteer members of
-the Technical Advisory Board (TAB), as well as a professional mediator
-acting as a neutral third party. The first task of the committee is to
-establish documented processes, which will be made public.
+the TAB, as well as a professional mediator acting as a neutral third
+party. The first task of the committee is to establish documented
+processes, which will be made public.
Any member of the committee, including the mediator, can be contacted
directly if a reporter does not wish to include the full committee in a
--
2.19.1
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Thomas Gleixner <tglx@linutronix.de>,
Olof Johansson <olof@lixom.net>, Chris Mason <clm@fb.com>,
Mishi Choudhary <mishi@linux.com>
Subject: [PATCH 3/7] Code of Conduct Interpretation: Properly reference the TAB correctly
Date: Sat, 20 Oct 2018 15:50:21 +0200 [thread overview]
Message-ID: <20181020135021.GD32218@kroah.com> (raw)
In-Reply-To: <20181020134908.GA32218@kroah.com>
We use the term "TAB" before defining it later in the document. Fix
that up by defining it at the first location.
Reported-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Acked-by: Chris Mason <clm@fb.com>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Theodore Ts'o <tytso@mit.edu>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
.../process/code-of-conduct-interpretation.rst | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst
index b14441711f7b..ecf84cd29735 100644
--- a/Documentation/process/code-of-conduct-interpretation.rst
+++ b/Documentation/process/code-of-conduct-interpretation.rst
@@ -45,11 +45,11 @@ regarding conduct issues.
Maintainers should be willing to help when problems occur, and work with
others in the community when needed. Do not be afraid to reach out to
-the TAB or other maintainers if you're uncertain how to handle
-situations that come up. It will not be considered a violation report
-unless you want it to be. If you are uncertain about approaching the
-TAB or any other maintainers, please reach out to our conflict mediator,
-Mishi Choudhary <mishi@linux.com>.
+the Technical Advisory Board (TAB) or other maintainers if you're
+uncertain how to handle situations that come up. It will not be
+considered a violation report unless you want it to be. If you are
+uncertain about approaching the TAB or any other maintainers, please
+reach out to our conflict mediator, Mishi Choudhary <mishi@linux.com>.
In the end, "be kind to each other" is really what the end goal is for
everybody. We know everyone is human and we all fail at times, but the
@@ -125,9 +125,9 @@ are listed at <URL>. Members can not access reports made before they
joined or after they have left the committee.
The initial Code of Conduct Committee consists of volunteer members of
-the Technical Advisory Board (TAB), as well as a professional mediator
-acting as a neutral third party. The first task of the committee is to
-establish documented processes, which will be made public.
+the TAB, as well as a professional mediator acting as a neutral third
+party. The first task of the committee is to establish documented
+processes, which will be made public.
Any member of the committee, including the mediator, can be contacted
directly if a reporter does not wish to include the full committee in a
--
2.19.1
next prev parent reply other threads:[~2018-10-20 13:52 UTC|newest]
Thread overview: 177+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 13:49 [Ksummit-discuss] [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document Greg Kroah-Hartman
2018-10-20 13:49 ` Greg Kroah-Hartman
2018-10-20 13:49 ` [Ksummit-discuss] [PATCH 1/7] Code of conduct: Fix wording around maintainers enforcing the code of conduct Greg Kroah-Hartman
2018-10-20 13:49 ` Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 2/7] Code of Conduct Interpretation: Add document explaining how the Code of Conduct is to be interpreted Greg Kroah-Hartman
2018-10-20 13:50 ` Greg Kroah-Hartman
2018-10-20 13:50 ` Greg Kroah-Hartman [this message]
2018-10-20 13:50 ` [PATCH 3/7] Code of Conduct Interpretation: Properly reference the TAB correctly Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 4/7] Code of Conduct: Provide links between the two documents Greg Kroah-Hartman
2018-10-20 13:50 ` Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 5/7] Code of Conduct Interpretation: Put in the proper URL for the committee Greg Kroah-Hartman
2018-10-20 13:50 ` Greg Kroah-Hartman
2018-10-20 19:01 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-10-20 19:01 ` Geert Uytterhoeven
2018-10-21 7:18 ` [Ksummit-discuss] " Greg KH
2018-10-21 7:18 ` Greg KH
2018-10-20 13:51 ` [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address Greg Kroah-Hartman
2018-10-20 13:51 ` Greg Kroah-Hartman
2018-10-20 18:28 ` [Ksummit-discuss] " Alan Cox
2018-10-20 18:28 ` Alan Cox
2018-10-20 18:45 ` [Ksummit-discuss] " Trond Myklebust
2018-10-20 18:45 ` Trond Myklebust
2018-10-20 19:14 ` jonsmirl
2018-10-20 19:14 ` jonsmirl
2018-10-21 8:27 ` Theodore Y. Ts'o
2018-10-21 8:27 ` Theodore Y. Ts'o
2018-10-21 9:23 ` Greg KH
2018-10-21 9:23 ` Greg KH
2018-10-20 19:24 ` Tim.Bird
2018-10-20 19:24 ` Tim.Bird
2018-10-20 20:07 ` Trond Myklebust
2018-10-20 20:07 ` Trond Myklebust
2018-10-21 0:13 ` Alan Cox
2018-10-21 0:13 ` Alan Cox
2018-10-21 6:19 ` Thomas Gleixner
2018-10-21 6:19 ` Thomas Gleixner
2018-10-20 20:13 ` James Bottomley
2018-10-20 20:13 ` James Bottomley
2018-10-20 13:51 ` [Ksummit-discuss] [PATCH 7/7] MAINTAINERS: Add an entry for the code of conduct Greg Kroah-Hartman
2018-10-20 13:51 ` Greg Kroah-Hartman
2018-10-21 21:20 ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-21 21:20 ` NeilBrown
2018-10-21 22:26 ` [Ksummit-discuss] " Josh Triplett
2018-10-21 22:26 ` Josh Triplett
2018-10-21 23:37 ` Theodore Y. Ts'o
2018-10-21 23:37 ` Theodore Y. Ts'o
2018-10-23 1:44 ` NeilBrown
2018-10-22 20:26 ` NeilBrown
2018-10-22 20:26 ` NeilBrown
2018-10-22 22:46 ` Theodore Y. Ts'o
2018-10-22 22:46 ` Theodore Y. Ts'o
2018-10-23 1:31 ` NeilBrown
2018-10-23 1:31 ` NeilBrown
2018-10-23 6:26 ` Dan Carpenter
2018-10-23 6:40 ` Al Viro
2018-10-23 6:40 ` Al Viro
2018-10-23 6:46 ` Dan Carpenter
2018-10-23 6:46 ` Dan Carpenter
2018-10-23 3:31 ` Al Viro
2018-10-23 3:31 ` Al Viro
2018-10-23 4:25 ` NeilBrown
2018-10-23 4:25 ` NeilBrown
2018-10-23 4:52 ` Al Viro
2018-10-23 4:52 ` Al Viro
2018-10-23 5:28 ` NeilBrown
2018-10-23 5:28 ` NeilBrown
2018-10-23 6:00 ` Al Viro
2018-10-23 6:00 ` Al Viro
2018-10-23 20:45 ` NeilBrown
2018-10-23 20:45 ` NeilBrown
2018-10-23 8:11 ` Theodore Y. Ts'o
2018-10-23 8:11 ` Theodore Y. Ts'o
2018-10-23 14:22 ` Rainer Fiebig
2018-10-23 14:22 ` Rainer Fiebig
2018-10-23 15:43 ` Theodore Y. Ts'o
2018-10-23 15:43 ` Theodore Y. Ts'o
2018-10-23 17:51 ` Rainer Fiebig
2018-10-23 21:14 ` NeilBrown
2018-10-23 21:14 ` NeilBrown
2018-10-24 12:16 ` Josh Triplett
2018-10-24 12:16 ` Josh Triplett
2018-10-25 21:14 ` NeilBrown
2018-10-25 21:14 ` NeilBrown
2018-10-27 1:10 ` Josh Triplett
2018-10-27 1:10 ` Josh Triplett
2018-10-28 21:48 ` NeilBrown
2018-10-28 21:48 ` NeilBrown
2018-11-01 16:45 ` Paul E. McKenney
2018-11-01 16:45 ` Paul E. McKenney
2018-11-01 21:11 ` Josh Triplett
2018-11-01 21:11 ` Josh Triplett
2018-11-02 13:13 ` Paul E. McKenney
2018-11-02 13:13 ` Paul E. McKenney
2018-11-01 21:50 ` NeilBrown
2018-11-02 13:33 ` Paul E. McKenney
2018-11-02 13:33 ` Paul E. McKenney
2018-11-03 8:36 ` NeilBrown
2018-11-03 8:36 ` NeilBrown
2018-11-03 17:37 ` Paul E. McKenney
2018-11-03 17:37 ` Paul E. McKenney
2018-11-03 21:06 ` NeilBrown
2018-11-03 21:06 ` NeilBrown
2018-11-03 22:23 ` Paul E. McKenney
2018-11-03 22:23 ` Paul E. McKenney
2018-11-02 13:52 ` James Bottomley
2018-11-03 9:19 ` Eric S. Raymond
2018-11-04 10:35 ` Geert Uytterhoeven
2018-11-04 10:35 ` Geert Uytterhoeven
2018-10-21 22:33 ` Joe Perches
2018-10-21 22:33 ` Joe Perches
2018-10-21 22:37 ` Randy Dunlap
2018-10-21 22:37 ` Randy Dunlap
2018-10-22 9:09 ` Rainer Fiebig
2018-10-22 9:09 ` Rainer Fiebig
2018-10-22 11:02 ` [Ksummit-discuss] " James Bottomley
2018-10-22 11:02 ` James Bottomley
2018-10-24 8:49 ` Laura Abbott
2018-10-24 8:49 ` Laura Abbott
2018-10-25 7:56 ` The linux devs can rescind their license grant visionsofalice
2018-10-25 8:19 ` [Ksummit-discuss] " Greg Kroah-Hartman
2018-10-25 8:19 ` Greg Kroah-Hartman
2018-10-25 19:39 ` Eric S. Raymond
2018-10-25 20:47 ` [Ksummit-discuss] " Theodore Y. Ts'o
2018-10-25 20:47 ` Theodore Y. Ts'o
2018-10-25 21:41 ` Eric S. Raymond
2018-10-25 22:12 ` [Ksummit-discuss] " NeilBrown
2018-10-25 22:12 ` NeilBrown
2018-10-25 22:38 ` Eric S. Raymond
2018-10-25 22:52 ` [Ksummit-discuss] " NeilBrown
2018-10-25 22:52 ` NeilBrown
2018-11-04 10:47 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-11-04 10:47 ` Geert Uytterhoeven
2018-10-25 23:06 ` Al Viro
2018-10-25 23:06 ` Al Viro
2018-10-26 2:28 ` Eric S. Raymond
2018-10-26 5:49 ` [Ksummit-discuss] " Al Viro
2018-10-26 5:49 ` Al Viro
2018-10-27 6:52 ` visionsofalice
2018-10-27 7:32 ` [Ksummit-discuss] " Al Viro
2018-10-27 7:32 ` Al Viro
2018-10-27 16:18 ` [Ksummit-discuss] " Tim.Bird
2018-10-27 16:18 ` Tim.Bird
2018-10-27 22:09 ` Jiri Kosina
2018-10-27 22:09 ` Jiri Kosina
[not found] ` <CAK2MWOtNUTjWy5pTcGco5DNurqNCc=9CfDJ-Ko-K+6HDC55ikg@mail.gmail.com>
2018-10-27 23:07 ` Eric S. Raymond
2018-10-27 23:40 ` Al Viro
2018-10-27 23:40 ` Al Viro
2018-10-28 21:13 ` NeilBrown
2018-10-28 21:13 ` NeilBrown
2018-10-25 23:32 ` Iván Chavero
2018-10-26 13:15 ` Eben Moglen
2018-10-26 15:50 ` Eric S. Raymond
2018-10-26 15:53 ` Eben Moglen
2018-10-26 17:32 ` visionsofalice
2018-10-26 18:31 ` Eben Moglen
2018-10-27 7:12 ` visionsofalice
2018-12-18 18:53 ` The linux devs can rescind their license grant. - Analysis published? visionsofalice
2018-10-26 10:34 ` The linux devs can rescind their license grant visionsofalice
2018-10-29 22:31 ` [Ksummit-discuss] " Bradley M. Kuhn
2018-10-29 22:31 ` Bradley M. Kuhn
2018-12-18 19:17 ` visionsofalice
2018-10-27 5:04 ` The linux devs can rescind their license grant. - Additional restrictive terms visionsofalice
2018-12-18 20:55 ` The CoC regime is a License violation " visionsofalice
2018-12-19 1:17 ` visionsofalice
2018-12-23 16:05 ` visionsofalice
2018-10-25 22:02 ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-25 22:02 ` NeilBrown
2018-10-25 8:06 ` [Ksummit-discuss] " Pavel Machek
2018-10-25 8:06 ` Pavel Machek
2018-10-25 11:20 ` Rainer Fiebig
2018-10-25 22:18 ` [Ksummit-discuss] " NeilBrown
2018-10-25 22:18 ` NeilBrown
2018-10-26 8:33 ` Rainer Fiebig
2018-10-26 22:40 ` [Ksummit-discuss] " NeilBrown
2018-10-26 22:40 ` NeilBrown
2018-10-27 11:49 ` Rainer Fiebig
2018-10-21 23:36 ` Eric S. Raymond
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=20181020135021.GD32218@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mishi@linux.com \
/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.