From: Keir Fraser <keir.xen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Matt Wilson <msw@amazon.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH 2 of 3] docs: use elinks to format markdown-generated html to text
Date: Thu, 30 Aug 2012 16:47:29 +0100 [thread overview]
Message-ID: <CC6549A1.3D42A%keir.xen@gmail.com> (raw)
In-Reply-To: <20543.35220.572436.112964@mariner.uk.xensource.com>
On 30/08/2012 16:41, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:
> Matt Wilson writes ("[Xen-devel] [PATCH 2 of 3] docs: use elinks to format
> markdown-generated html to text"):
>> Markdown, while easy to read and write, isn't the most consumable
>> format for users reading documentation on a terminal. This patch uses
>> lynx to format markdown produced HTML into text files.
> ...
>> txt/%.txt: %.markdown
>> - $(INSTALL_DIR) $(@D)
>> - cp $< $@.tmp
>> - $(call move-if-changed,$@.tmp,$@)
>> + @$(INSTALL_DIR) $(@D)
>> + set -e ; \
>> + if which $(MARKDOWN) >/dev/null 2>&1 && \
>> + which $(HTMLDUMP) >/dev/null 2>&1 ; then \
>> + echo "Running markdown to generate $*.txt ... "; \
>
> So now we have two efforts to try to find markdown, one in configure
> and one here.
>
> Keir, would it be OK if we simply declared that you must run configure
> to "make docs" ?
Yes!
-- Keir
> Ian.
next prev parent reply other threads:[~2012-08-30 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 21:01 [PATCH 0 of 3] improve checking for documentation tools and formatting Matt Wilson
2012-08-29 21:01 ` [PATCH 1 of 3] tools: check for documentation generation tools at configure time Matt Wilson
2012-08-30 15:39 ` Ian Jackson
2012-08-29 21:01 ` [PATCH 2 of 3] docs: use elinks to format markdown-generated html to text Matt Wilson
2012-08-30 15:41 ` Ian Jackson
2012-08-30 15:47 ` Keir Fraser [this message]
2012-08-30 16:41 ` Matt Wilson
2012-08-30 15:47 ` Ian Campbell
2012-08-30 16:54 ` Matt Wilson
2012-08-29 21:01 ` [PATCH 3 of 3] tools/docs: allow markdown_py to be used Matt Wilson
2012-08-30 15:40 ` Ian Jackson
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=CC6549A1.3D42A%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=msw@amazon.com \
--cc=xen-devel@lists.xen.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).