Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: tiwai@suse.de (Takashi Iwai)
Subject: [PATCH 0/2] Documentation: add asciidoctor support
Date: Tue, 05 Jun 2018 16:41:19 +0200	[thread overview]
Message-ID: <s5h8t7tpa7k.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180412110238.30717-1-tiwai@suse.de>

On Thu, 12 Apr 2018 13:02:36 +0200,
Takashi Iwai wrote:
> 
> Hi,
> 
> this is a patchset to add the support for asciidoctor to generate
> documents.  asciidoc is based on python2, and its future isn't clear,
> so as a plan-B, we can use asciidoctor instead.
> 
> The asciidoctor support is opt-in, the default is still kept for
> asciidoc for now.

Just a gentle reminder about this patchset.

I've seen reviewed-by from Sagi, but couldn't find any other
reactions, also not on github repo.

Let me know if I need to fix or resend.


thanks,

Takashi


> 
> 
> thanks,
> 
> Takashi
> 
> ===
> 
> Takashi Iwai (2):
>   Documentation: fix title markers
>   Documentation: allow to format with asciidoctor
> 
>  Documentation/Makefile                   |   13 +++++++++++++
>  Documentation/asciidoctor-extensions.rb  |   29 +++++++++++++++++++++++++++++
>  Documentation/nvme-discover.txt          |    2 +-
>  Documentation/nvme-huawei-id-ctrl.txt    |    2 +-
>  Documentation/nvme-wdc-id-ctrl.txt       |    2 +-
>  Documentation/nvme-wdc-purge-monitor.txt |    2 +-
>  Documentation/nvme-wdc-purge.txt         |    2 +-
>  7 files changed, 47 insertions(+), 5 deletions(-)
> 

  parent reply	other threads:[~2018-06-05 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 11:02 [PATCH 0/2] Documentation: add asciidoctor support Takashi Iwai
2018-04-12 11:02 ` [PATCH 1/2] Documentation: fix title markers Takashi Iwai
2018-04-12 11:02 ` [PATCH 2/2] Documentation: allow to format with asciidoctor Takashi Iwai
2018-04-12 15:54 ` [PATCH 0/2] Documentation: add asciidoctor support Sagi Grimberg
2018-06-05 14:41 ` Takashi Iwai [this message]
2018-06-05 14:42   ` Johannes Thumshirn
2018-06-05 15:02     ` Keith Busch
2018-06-05 15:12       ` Takashi Iwai

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=s5h8t7tpa7k.wl-tiwai@suse.de \
    --to=tiwai@suse.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