From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH] Documentation: set a base URL for relative links
Date: Wed, 02 Dec 2009 18:16:08 -0800 [thread overview]
Message-ID: <7vy6lk7qfr.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20091203015005.GH23717@inocybe.localdomain> (Todd Zullinger's message of "Wed\, 2 Dec 2009 20\:50\:05 -0500")
Todd Zullinger <tmz@pobox.com> writes:
> I don't know the doc toolchain well enough to know how best to fix
> this without breaking anything. It would be ideal if the base URL
> used was substituted and controllable via make variables. That would
> allow packagers to make it point to the on-disk documentation and make
> git's documentation even easier to use when disconnected.
Thanks. It indeed appears that update to FC11 at k.org brought a few
issues to the documentation area.
I think we can do something like this and let distro people to decide what
URL to use.
Documentation/Makefile | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 3f59952..abb75eb 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -104,6 +104,10 @@ ifdef DOCBOOK_SUPPRESS_SP
XMLTO_EXTRA += -m manpage-suppress-sp.xsl
endif
+ifdef MAN_BASE_URL
+XMLTO_EXTRA += --stringparam man.base.url.for.relative.links=$(MAN_BASE_URL)
+endif
+
# If your target system uses GNU groff, it may try to render
# apostrophes as a "pretty" apostrophe using unicode. This breaks
# cut&paste, so you should set GNU_ROFF to force them to be ASCII
prev parent reply other threads:[~2009-12-03 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 1:50 [RFC PATCH] Documentation: set a base URL for relative links Todd Zullinger
2009-12-03 2:16 ` Junio C Hamano [this message]
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=7vy6lk7qfr.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tmz@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