git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] Documentation: Replace @@GIT_VERSION@@ in documentation

From
Junio C Hamano <junkio@cox.net>
Date
Mar 26, 2007, 05:33 UTC
Message-ID
<7v7it41scp.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<11748238102228-git-send-email-frank@lichtenheld.de>
Frank Lichtenheld <frank@lichtenheld.de> writes:
Show 15 quoted lines
>  %.html : %.txt
>  	$(ASCIIDOC) -b xhtml11 -d manpage -f asciidoc.conf $(ASCIIDOC_EXTRA) $<
> +	sed -e 's/@@GIT_VERSION@@/$(GIT_VERSION)/g' $@ >$@+
> +	mv $@+ $@
>  
>  %.1 %.7 : %.xml
>  	xmlto -m callouts.xsl man $<
>  
>  %.xml : %.txt
>  	$(ASCIIDOC) -b docbook -d manpage -f asciidoc.conf $<
> +	sed -e 's/@@GIT_VERSION@@/$(GIT_VERSION)/g' $@ >$@+
> +	mv $@+ $@
>  
>  user-manual.xml: user-manual.txt user-manual.conf
>  	$(ASCIIDOC) -b docbook -d book $<

Sorry, but these compositions are wrong, as the build procedure can die after asciidoc finishes but before it manages to finish sed/mv. The next make invocation would not know that the previous one did not complete and would assume that the build product %.html or %.xml are up to date.

Ideally if we can persuade asciidoc to output to its stdout, we could do this:

	rm -f $@+ $@
        $(ASCIIDOC) --to-stdout ... | sed -e $(script) >$@+
        mv $@+ $@
Previous: Junio C HamanoNext: Junio C Hamano
Message 10 of 11 in “Documentation: Allow @@GIT_VERSION@@ in asciidoc.conf”
  1. 1/2 Documentation: Allow @@GIT_VERSION@@ in asciidoc.confFrank Lichtenheld, Mar 23, 2007
  2. 2/2 Documentation: Add version information to man pagesFrank Lichtenheld, Mar 23, 2007
  3. Junio C HamanoMar 23, 2007
  4. Frank LichtenheldMar 24, 2007
  5. Brian GernhardtMar 24, 2007
  6. Junio C HamanoMar 24, 2007
  7. 1/2 Documentation: Replace @@GIT_VERSION@@ in documentationFrank Lichtenheld, Mar 25, 2007
  8. 2/2 Documentation: Add version information to man pagesFrank Lichtenheld, Mar 25, 2007
  9. Junio C HamanoMar 27, 2007
  10. Junio C HamanoMar 26, 2007
  11. Junio C HamanoMar 26, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.