From: Jonathan Corbet <corbet@lwn.net>
To: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
Cc: linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Stephan Mueller <smueller@chronox.de>,
Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc
Date: Thu, 23 Jul 2015 22:29:12 +0200 [thread overview]
Message-ID: <20150723222912.50ba8f9f@lwn.net> (raw)
In-Reply-To: <1437675387-25719-1-git-send-email-danilo.cesar@collabora.co.uk>
On Thu, 23 Jul 2015 15:16:23 -0300
Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk> wrote:
> This series add supports for hyperlink cross-references on Docbooks and
> an optional markup syntax for in-source Documentation.
I like the idea; just be warned that it's likely to be a week or two and
one more ocean crossing before I can take a serious look at this...
Thanks,
jon
next prev parent reply other threads:[~2015-07-23 20:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 18:16 [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 1/4] scripts/kernel-doc: Adding cross-reference links to html documentation Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 2/4] scripts/kernel-doc: Replacing highlights hash by an array Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 3/4] scripts/kernel-doc: Adding infrastructure for markdown support Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 4/4] drm/doc: Convert to markdown Danilo Cesar Lemes de Paula
2015-07-23 20:29 ` Jonathan Corbet [this message]
2015-08-13 23:09 ` [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc Danilo Cesar Lemes de Paula
2015-08-13 23:20 ` Jonathan Corbet
2015-08-14 17:26 ` Danilo Cesar Lemes de Paula
2015-07-25 10:20 ` Stephan Mueller
2015-07-28 19:12 ` Danilo Cesar Lemes de Paula
2015-07-28 19:45 ` [PATCH v2 " Danilo Cesar Lemes de Paula
2015-07-28 19:45 ` [PATCH v2 1/4] scripts/kernel-doc: Adding cross-reference links to html documentation Danilo Cesar Lemes de Paula
2015-08-17 4:10 ` Jonathan Corbet
2015-08-17 13:06 ` Danilo Cesar Lemes de Paula
2015-07-28 19:45 ` [PATCH v2 2/4] scripts/kernel-doc: Replacing highlights hash by an array Danilo Cesar Lemes de Paula
2015-11-17 10:40 ` Mauro Carvalho Chehab
2015-11-17 14:44 ` Jonathan Corbet
2015-11-17 15:29 ` Mauro Carvalho Chehab
2015-11-17 15:48 ` Danilo Cesar Lemes de Paula
2015-11-18 0:21 ` Jonathan Corbet
2015-11-18 9:14 ` Mauro Carvalho Chehab
2015-07-28 19:45 ` [PATCH v2 3/4] scripts/kernel-doc: Adding infrastructure for markdown support Danilo Cesar Lemes de Paula
2015-07-28 19:45 ` [PATCH v2 4/4] drm/doc: Convert to markdown Danilo Cesar Lemes de Paula
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=20150723222912.50ba8f9f@lwn.net \
--to=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=danilo.cesar@collabora.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=herbert@gondor.apana.org.au \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@infradead.org \
--cc=smueller@chronox.de \
/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