[PATCH] Clarify use of mailing list

[PATCH] Clarify use of mailing list

[Kanta Vekaria]

- Create new mailing list section
- Add mailing list in contribution section

Signed-off-by: Kanta Vekaria <kanta.vekaria-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
---
 README.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 8ff30c4..83a5188 100644
--- a/README.md
+++ b/README.md
@@ -2,12 +2,12 @@
 
 The latest release of the specification can be found at http://devicetree.org/ or https://github.com/devicetree-org/devicetree-specification-released
 
-Mailing list:
-   devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-   http://vger.kernel.org/vger-lists.html#devicetree-spec
-
 This [repository](https://github.com/devicetree-org/devicetree-specification) holds the source for the generation of the Devicetree Specification using Sphinx and LaTeX. 
 
+## Mailing list: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org ##
+   * Use this mailing list for submitting patches, questions and general discussion
+   * Sign up to the mailing list at http://vger.kernel.org/vger-lists.html#devicetree-spec
+
 ## Build Instructions ##
 
 Requirements:
@@ -75,6 +75,7 @@ in the LICENSE and NOTICE file or online at:
 http://www.apache.org/licenses/LICENSE-2.0
 
 ## Contributions ##
+Please submit all patches to the mailing list devicetree-spec-u79uwXL29TaiAVqoAR/hOA@public.gmane.org
 Contributions to the Devicetree Specification are managed by the gatekeepers,
 Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> and Rob Herring <rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
 
-- 
2.7.4 (Apple Git-66)

Re: [PATCH] Clarify use of mailing list

[Daniel Bünzli]

If you don't want people filling in github issues and submitting pull requests I suggest you explicitely say so after the first github mention. 

Best, 

Daniel

Re: [PATCH] Clarify use of mailing list

[Rob Herring]

On Thu, Jul 21, 2016 at 6:14 PM, Daniel Bünzli
<daniel.buenzli-llsTEZYSXZwXXHkOk0aIfQ@public.gmane.org> wrote:
> If you don't want people filling in github issues and submitting pull requests I suggest you explicitely say so after the first github mention.

It's not a case of never. PR are fine, but patches still have to go to
the list for review first. Issues are fine too, but patches will more
likely get some action. The request to publish html docs is a good
example for what can/should be an issue. The other issues should be
patches IMO. Even if you don't know for sure the right fix, write a
patch for what you think is correct or ask on the list.

Rob

Re: [PATCH] Clarify use of mailing list

[Daniel Bünzli]

Le vendredi, 22 juillet 2016 à 17:11, Rob Herring a écrit :
> It's not a case of never. PR are fine, but patches still have to go to
> the list for review first.  

So why not simply send a link to the PR to the mailing list ? I'm not a great fan of github's interface but it's still better than reading patches in my email client (it allows me to easily get access to the patch's surrounding context which is important for checking consistency of the proposal). Also send patch to mailing list then PR seems a little bit more bureaucratic than it should be for the contributor.

Best,  

Daniel