From: Jonas Fonseca <fonseca@diku.dk>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Alp Toker <alp@atoker.com>
Subject: [PATCH] Make asciidoc related rules depend on asciidoc.conf
Date: Sat, 15 Jul 2006 09:44:25 +0200 [thread overview]
Message-ID: <20060715074425.GA2661@diku.dk> (raw)
In-Reply-To: <7v3bd3ois4.fsf@assigned-by-dhcp.cox.net>
Any rule running asciidoc, whether using -f asciidoc.conf or not,
will read asciidoc.conf. Make such rules depend on asciidoc.conf.
Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
---
Junio C Hamano <junkio@cox.net> wrote Fri, Jul 14, 2006:
> Alp is right -- the comments in [attributes] section after the
> definition do appear in the output, even with asciidoc 7.1.2, so
> here is a replacement proposal from me.
Am using the same setup as Alp (AsciiDoc 7.0.2 on Ubuntu Dapper), so I
was a bit curious that I could not see that. So I guess I compiled the
docs first and later decided to add the comments which then didn't cause
a recompilation.
I don't know if there should be a dependency on asciidoc.conf in every
rule calling asciidoc. Could be annoying if you are only making a minor
change.
---
diff --git a/Documentation/Makefile b/Documentation/Makefile
index cc83610..ce6c6cf 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -76,18 +76,18 @@ README: ../README
clean:
rm -f *.xml *.html *.1 *.7 howto-index.txt howto/*.html doc.dep README
-%.html : %.txt
+%.html : %.txt asciidoc.conf
asciidoc -b xhtml11 -d manpage -f asciidoc.conf $<
%.1 %.7 : %.xml
xmlto -m callouts.xsl man $<
-%.xml : %.txt
+%.xml : %.txt asciidoc.conf
asciidoc -b docbook -d manpage -f asciidoc.conf $<
git.html: git.txt README
-glossary.html : glossary.txt sort_glossary.pl
+glossary.html : glossary.txt sort_glossary.pl asciidoc.conf
cat $< | \
perl sort_glossary.pl | \
asciidoc -b xhtml11 - > glossary.html
@@ -97,12 +97,12 @@ howto-index.txt: howto-index.sh $(wildca
sh ./howto-index.sh $(wildcard howto/*.txt) >$@+
mv $@+ $@
-$(patsubst %,%.html,$(ARTICLES)) : %.html : %.txt
+$(patsubst %,%.html,$(ARTICLES)) : %.html : %.txt asciidoc.conf
asciidoc -b xhtml11 $*.txt
WEBDOC_DEST = /pub/software/scm/git/docs
-$(patsubst %.txt,%.html,$(wildcard howto/*.txt)): %.html : %.txt
+$(patsubst %.txt,%.html,$(wildcard howto/*.txt)): %.html : %.txt asciidoc.conf
rm -f $@+ $@
sed -e '1,/^$$/d' $? | asciidoc -b xhtml11 - >$@+
mv $@+ $@
--
Jonas Fonseca
prev parent reply other threads:[~2006-07-15 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 10:24 [PATCH] Revert "Documentation: Fix ssh://[user@]host.xz URL" Alp Toker
2006-07-14 10:24 ` [PATCH] Documentation: Fix ssh:// URLs in generated documentation Alp Toker
2006-07-14 10:24 ` [PATCH] Documentation: Minor capitalization typofix Alp Toker
2006-07-14 21:46 ` [PATCH] Documentation: Fix ssh:// URLs in generated documentation Junio C Hamano
2006-07-14 21:50 ` [PATCH] urls.txt: Use substitution to escape square brackets Jonas Fonseca
2006-07-14 22:07 ` Junio C Hamano
2006-07-14 23:01 ` Alp Toker
2006-07-14 23:13 ` Junio C Hamano
2006-07-14 23:57 ` Alp Toker
2006-07-14 23:42 ` Junio C Hamano
2006-07-15 0:38 ` Alp Toker
2006-07-15 7:44 ` Jonas Fonseca [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=20060715074425.GA2661@diku.dk \
--to=fonseca@diku.dk \
--cc=alp@atoker.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).