That means that for the patch [6/8], which adds content-type to the
text files, to be complete, it needs to update Makefile to produce
html files from them.
IMHO also for the new files in ./technical html should be created because
now as we have asciidoc markup why not also use it.
Thomas Ackermann th.acke...@arcor.de writes:
Yes; in e2399e9 the following hunks where left out from the patch to
update-hook-example.txt:
@@ -111,12 +114,12 @@ then
info Found matching head pattern: '$head_pattern'
for user_pattern in $user_patterns; do
- info
- Original Nachricht
Von: Junio C Hamano gits...@pobox.com
An: Thomas Ackermann th.acke...@arcor.de
Datum: 17.10.2012 00:11
Betreff: Re: [Patch v3 0/8] Create single PDF for all HTML files
I (and other people who wrote documentation, I suspect, as well)
feel somewhat
Thomas Ackermann th.acke...@arcor.de writes:
BTW1: As only the changes in the doc files where cherry-picked, currently on
pu howto-index.sh
will create invalid links in howto-index.html because it scans all .txt-files
in ./howto for
'Content-type: text/asciidoc' and if found, creates a
4 matches
Mail list logo