From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Peter Zijlstra <peterz@infradead.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] doc: Explain light-handed markup preference a bit better
Date: Mon, 12 Dec 2016 10:54:47 -0700 [thread overview]
Message-ID: <20161212105447.25d1ffe7@lwn.net> (raw)
In-Reply-To: <CAKMK7uFhDe5gKTK9SsNhy9ipdXPfA=-BYNBac+7N-gO_Wcat=A@mail.gmail.com>
On Thu, 8 Dec 2016 23:06:57 +0100
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Hm yeah, separate conversion section makes sense. In that case I'll
> adopt Jani's suggestion for more terseness in overview document, and
> we can merge Mauro's proposal (or something like it) on top. And I'll
> try to rebase onto latest doc-next too ;-)
>
> Does that sound like a plan, before I head of and respin v4?
It sounds like a good plan to me.
jon
next prev parent reply other threads:[~2016-12-12 17:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 15:42 [PATCH] doc: Explain light-handed markup preference a bit better Daniel Vetter
2016-12-07 19:39 ` Jonathan Corbet
2016-12-08 9:10 ` Mauro Carvalho Chehab
2016-12-08 22:06 ` Daniel Vetter
2016-12-12 17:47 ` Mauro Carvalho Chehab
2016-12-12 17:54 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-14 13:46 Daniel Vetter
2016-11-29 9:23 Daniel Vetter
2016-11-29 10:28 ` Markus Heiser
2016-11-29 11:54 ` Mauro Carvalho Chehab
2016-11-29 10:38 ` Jani Nikula
2016-11-29 11:43 ` Mauro Carvalho Chehab
2016-11-29 15:08 ` Jani Nikula
2016-12-07 15:45 ` Daniel Vetter
2016-11-29 13:17 ` Daniel Vetter
2016-12-06 7:52 ` Peter Zijlstra
2016-12-07 15:45 ` Daniel Vetter
2016-11-28 16:16 Daniel Vetter
2016-11-28 17:51 ` Mauro Carvalho Chehab
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=20161212105447.25d1ffe7@lwn.net \
--to=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=hch@infradead.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=peterz@infradead.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