Hi,
this is v3 of my patch series for creating a single PDF for all
git documentation files.
There are only 2 changes since v2 (thanks to Junio for pointing me at these
issues) :
- The over-long lines in git-bisect-lk2009.txt where shortened by abbreviating
the SHA1s.
- Pretty-printing the shel
Thomas Ackermann writes:
> this is v3 of my patch series for creating a single PDF for all
> git documentation files.
>
> There are only 2 changes since v2 (thanks to Junio for pointing me at these
> issues) :
> - The over-long lines in git-bisect-lk2009.txt where shortened by
> abbreviating th
- Original Nachricht
Von: Junio C Hamano
An: Thomas Ackermann
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 offended by the word "
Thomas Ackermann 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 reference to a ht
>
> 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 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 "Checking user:
6 matches
Mail list logo