From: "Daniel Bünzli" <daniel.buenzli-llsTEZYSXZwXXHkOk0aIfQ@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Kanta Vekaria"
<kanta.vekaria-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"devicetree-spec@vger.kernel.org"
<devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Grant Likely"
<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
grunk-BIb/Zk+JBDab9/CCa1Sigw@public.gmane.org
Subject: Re: [PATCH] Clarify use of mailing list
Date: Fri, 22 Jul 2016 17:21:18 +0200 [thread overview]
Message-ID: <9FF0B2339BD04B5DB4D82988EECA4EEC@erratique.ch> (raw)
In-Reply-To: <CAL_JsqKOv0hbZ5z_xOz3VeDtT18jfm+6wE-uVnoLfZ7u-LxUHQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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
prev parent reply other threads:[~2016-07-22 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 13:57 [PATCH] Clarify use of mailing list Kanta Vekaria
[not found] ` <1469109424-2482-1-git-send-email-kanta.vekaria-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-07-21 23:14 ` Daniel Bünzli
[not found] ` <B45181E874114CF5A1FAB4752DCAFEAB-llsTEZYSXZwXXHkOk0aIfQ@public.gmane.org>
2016-07-22 15:11 ` Rob Herring
[not found] ` <CAL_JsqKOv0hbZ5z_xOz3VeDtT18jfm+6wE-uVnoLfZ7u-LxUHQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-22 15:21 ` Daniel Bünzli [this message]
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=9FF0B2339BD04B5DB4D82988EECA4EEC@erratique.ch \
--to=daniel.buenzli-llstezysxzwxxhkok0aifq@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=grunk-BIb/Zk+JBDab9/CCa1Sigw@public.gmane.org \
--cc=kanta.vekaria-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).