From: Matt Wilson <msw@amazon.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: [PATCH 0 of 2 v2] improve checking for documentation tools and formatting
Date: Thu, 30 Aug 2012 11:59:58 -0700 [thread overview]
Message-ID: <patchbomb.1346353198@u002268147cd4502c336d.ant.amazon.com> (raw)
This version makes running ./configure a prerequisite for building
documentation. If a tool is not detected by ./configure and is not
specified by the user, the make variable will be empty. So I've
switched to using make conditionals instead of which(1).
Matt
next reply other threads:[~2012-08-30 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 18:59 Matt Wilson [this message]
2012-08-30 18:59 ` [PATCH 1 of 2 v2] tools: check for documentation generation tools at configure time Matt Wilson
2012-08-31 9:25 ` Ian Campbell
2012-08-31 12:30 ` Ian Campbell
2012-09-04 2:13 ` Matt Wilson
2012-08-31 12:30 ` Ian Campbell
2012-08-30 19:00 ` [PATCH 2 of 2 v2] docs: use elinks to format markdown-generated html to text Matt Wilson
2012-08-31 9:26 ` Ian Campbell
2012-09-04 2:12 ` Matt Wilson
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=patchbomb.1346353198@u002268147cd4502c336d.ant.amazon.com \
--to=msw@amazon.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.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).