From: Masami Hiramatsu <mhiramat@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Steven Rostedt <rostedt@goodmis.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [v2 0/1] Documentation: bootconfig: Documentation updates
Date: Fri, 28 Feb 2020 23:55:28 +0900 [thread overview]
Message-ID: <20200228235528.acfc091ee58d4d685a119f4f@kernel.org> (raw)
In-Reply-To: <0d7d201c-e313-6129-7cfa-4e61eb31342d@web.de>
On Fri, 28 Feb 2020 15:05:42 +0100
Markus Elfring <Markus.Elfring@web.de> wrote:
> > So, if you are interested in it, I don't stop you to write it up.
>
> Will the collaboration continue anyhow?
It's your turn. "ask not what your community can do for you - ask what you can do for your community." :)
Collaboration is not just talking, but move things step forward.
> Will the clarification become more constructive for remaining challenges?
If you think so, you can send a patch for it.
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2020-02-28 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 8:30 [PATCH v2 0/1] Documentation: bootconfig: Documentaiton updates Masami Hiramatsu
2020-02-28 8:30 ` [PATCH v2] Documentation: bootconfig: Update boot configuration documentation Masami Hiramatsu
2020-02-28 10:00 ` Markus Elfring
2020-02-28 13:26 ` Masami Hiramatsu
2020-02-28 11:55 ` [v2] " Markus Elfring
2020-02-29 5:59 ` [PATCH v2] " Randy Dunlap
2020-03-02 6:52 ` Masami Hiramatsu
2020-03-02 7:06 ` Randy Dunlap
2020-03-02 8:23 ` [v2] " Markus Elfring
2020-02-28 9:00 ` [v2 0/1] Documentation: bootconfig: Documentation updates Markus Elfring
2020-02-28 13:23 ` Masami Hiramatsu
2020-02-28 14:05 ` Markus Elfring
2020-02-28 14:55 ` Masami Hiramatsu [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=20200228235528.acfc091ee58d4d685a119f4f@kernel.org \
--to=mhiramat@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.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).