xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: "Fioravante, Matthew E." <Matthew.Fioravante@jhuapl.edu>,
	Matt Wilson <msw@amazon.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH V2 4/5] docs: check for documentation generation tools in docs/configure.
Date: Thu, 24 Jan 2013 14:24:59 +0100	[thread overview]
Message-ID: <5101362B.9050407@citrix.com> (raw)
In-Reply-To: <1358760816-13146-4-git-send-email-ian.campbell@citrix.com>

On 21/01/13 10:33, Ian Campbell wrote:
> It is sometimes hard to discover all the optional tools that should be
> on a system to build all available Xen documentation. By checking for
> documentation generation tools at ./configure time and displaying a
> warning, Xen packagers will more easily learn about new optional build
> dependencies, like markdown, when they are introduced.
> 
> Based on a patch by Matt Wilson. Changed to use a separate
> docs/configure which is called from the top-level in the same manner
> as stubdoms.
> 
> Rerun autogen.sh and "git add docs/configure" after applying this patch.
> 
> Signed-off-by: Matt Wilson <msw@amazon.com>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Acked-by: Matt Wilson <msw@amazon.com>
>   (For the change to introduce docs/configure)
Acked-by: Roger Pau Monné <roger.pau@citrix.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-01-24 13:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21  9:32 [PATCH 0/5 V2] install into /usr/local and docs/configure Ian Campbell
2013-01-21  9:33 ` [PATCH V2 1/5] tools+stubdom: install under /usr/local by default Ian Campbell
2013-01-24 13:03   ` Ian Campbell
2013-01-21  9:33 ` [PATCH V2 2/5] docs: Remove xen-api docs Ian Campbell
2013-01-24 13:23   ` Roger Pau Monné
2013-01-25  9:06     ` Ian Campbell
2013-01-25  9:29       ` Roger Pau Monné
2013-01-25 10:06         ` Ian Campbell
2013-01-21  9:33 ` [PATCH V2 3/5] docs: drop doxygen stuff Ian Campbell
2013-01-24 13:24   ` Roger Pau Monné
2013-01-21  9:33 ` [PATCH V2 4/5] docs: check for documentation generation tools in docs/configure Ian Campbell
2013-01-24 13:24   ` Roger Pau Monné [this message]
2013-01-21  9:33 ` [PATCH V2 5/5] build: cleanup configure detritus at toplevel and stubdom Ian Campbell
2013-01-24 13:20   ` Roger Pau Monné

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=5101362B.9050407@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Matthew.Fioravante@jhuapl.edu \
    --cc=ian.campbell@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).