From: Randy Dunlap <rdunlap@xenotime.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Andy Whitcroft <apw@canonical.com>,
linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docbook: need xmldoclinks for all doc types
Date: Tue, 15 Jun 2010 08:36:23 -0700 [thread overview]
Message-ID: <20100615083623.2dbaab24.rdunlap@xenotime.net> (raw)
In-Reply-To: <1276563314.14011.361.camel@localhost>
On Tue, 15 Jun 2010 01:55:14 +0100 Ben Hutchings wrote:
> Andy Whitcroft wrote:
> > We need the xmldoclinks built for any document types built from the
> > XML sources.
>
> Indeed we do. So make the XML files depend on xmldoclinks.
The patch description tells me what but not why.
IOW, what error is this fixing and how do I produce that error
when this patch is not applied?
Thanks.
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> Acked-by: Andy Whitcroft <apw@canonical.com>
> ---
> --- a/Documentation/DocBook/Makefile
> +++ b/Documentation/DocBook/Makefile
> @@ -35,7 +35,7 @@ PS_METHOD = $(prefer-db2x)
> PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs cleandocs xmldoclinks
>
> BOOKS := $(addprefix $(obj)/,$(DOCBOOKS))
> -xmldocs: $(BOOKS) xmldoclinks
> +xmldocs: $(BOOKS)
> sgmldocs: xmldocs
>
> PS := $(patsubst %.xml, %.ps, $(BOOKS))
> @@ -95,7 +95,7 @@ define rule_docproc
> ) > $(dir $@).$(notdir $@).cmd
> endef
>
> -%.xml: %.tmpl FORCE
> +%.xml: %.tmpl xmldoclinks FORCE
> $(call if_changed_rule,docproc)
>
> ###
>
> --
> Ben Hutchings
> Once a job is fouled up, anything done to improve it makes it worse.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-06-15 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 11:01 [PATCH 1/1] " Andy Whitcroft
2010-06-14 11:15 ` Ben Hutchings
2010-06-14 12:20 ` Andy Whitcroft
2010-06-15 0:55 ` [PATCH] " Ben Hutchings
2010-06-15 15:36 ` Randy Dunlap [this message]
2010-06-16 0:46 ` Ben Hutchings
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=20100615083623.2dbaab24.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=ben@decadent.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®