From: Dave Borowitz <dborowitz@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation/Makefile: Allow custom XMLTO binary
Date: Wed, 19 Sep 2012 13:49:19 -0700 [thread overview]
Message-ID: <CAD0k6qTMm7MKLYOOMaB72cWc=Z8nJfe8qseWfyM6x_NzCorgZg@mail.gmail.com> (raw)
In-Reply-To: <7vehlxhp0v.fsf@alter.siamese.dyndns.org>
On Wed, Sep 19, 2012 at 10:59 AM, Junio C Hamano <gitster@pobox.com> wrote:
> dborowitz@google.com writes:
>
>> From: Dave Borowitz <dborowitz@google.com>
>>
>> Signed-off-by: Dave Borowitz <dborowitz@google.com>
>> ---
>
> Thanks; the patch sort-of makes sense but makes me wonder what your
> use case is. Do you have xmlto2 program you want to use in place of
> xmlto or you have xmlto but not on your $PATH?
The latter; I can easily symlink it into my $PATH of course. But since
I was already specifying ASCIIDOC on the make command line for the
same reason, I was surprised to find I couldn't also specify XMLTO,
hence the patch.
>> Documentation/Makefile | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/Makefile b/Documentation/Makefile
>> index cf5916f..b045628 100644
>> --- a/Documentation/Makefile
>> +++ b/Documentation/Makefile
>> @@ -47,6 +47,7 @@ man7dir=$(mandir)/man7
>> ASCIIDOC=asciidoc
>> ASCIIDOC_EXTRA =
>> MANPAGE_XSL = manpage-normal.xsl
>> +XMLTO=xmlto
>> XMLTO_EXTRA =
>> INSTALL?=install
>> RM ?= rm -f
>> @@ -245,7 +246,7 @@ manpage-base-url.xsl: manpage-base-url.xsl.in
>>
>> %.1 %.5 %.7 : %.xml manpage-base-url.xsl
>> $(QUIET_XMLTO)$(RM) $@ && \
>> - xmlto -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $<
>> + $(XMLTO) -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $<
>>
>> %.xml : %.txt
>> $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \
next prev parent reply other threads:[~2012-09-19 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 17:06 [PATCH] Documentation/Makefile: Allow custom XMLTO binary dborowitz
2012-09-19 17:59 ` Junio C Hamano
2012-09-19 20:49 ` Dave Borowitz [this message]
2012-09-19 23:27 ` Junio C Hamano
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='CAD0k6qTMm7MKLYOOMaB72cWc=Z8nJfe8qseWfyM6x_NzCorgZg@mail.gmail.com' \
--to=dborowitz@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).