Re: "docs: stop using asciidoc no-inline-literal" breaks asciidoc 8.2.5
- From
Thomas Rast <trast@inf.ethz.ch>
- Date
- May 29, 2012, 12:03 UTC
- Message-ID
- <87ehq3mbxg.fsf@thomas.inf.ethz.ch>
- In-Reply-To
- <CACBZZX7Y-NTzRP1KYy=eEHTsLHTrzxGms61anXSHVbyCSPgurw@mail.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> Jeff King's 6cf378f0cbe7c7f944637892caeb9058c90a185a broke my Git > build on CentOS 5.5. The patch suggests that it only breaks > compatibility with asciidoc 7 but that isn't actually the case.
The commit message of 6cf378f0 is not correct in that respect. My ancient 71c020c5 has the right numbers: asciidoc 8.4.1 is the one that introduced the new inline-literal behavior. Based on my little survey in
http://thread.gmane.org/gmane.comp.version-control.git/191738/focus=191790
we decided that "nobody" really uses such an old asciidoc any more. Evidently you are a counterexample.
> I suggest just ejecting this patch and trying again, these RedHat > systems are still used in a lot of environments, especially by various > companies.
Do you/they have to *build* the docs, as opposed to using the prebuilt ones coming from Junio? Perhaps we can make it so 'make man' refuses to run if asciidoc is too old, and give a message to the effect that you should 'make quick-install-man' instead.
Otherwise we'll be working around the f{asterisk}{asterisk}{asterisk}ing quoting rules for years to come.
--
Thomas Rast
trast@{inf,student}.ethz.ch