Re: [PATCH v2 0/7] Macros for Asciidoctor support

2017-01-25 Thread brian m. carlson
On Wed, Jan 25, 2017 at 06:30:00PM -0500, Jeff King wrote: > On Wed, Jan 25, 2017 at 11:19:26PM +, brian m. carlson wrote: > > > On Wed, Jan 25, 2017 at 04:35:44PM -0500, Jeff King wrote: > > > On Wed, Jan 25, 2017 at 02:28:55PM +0100, Johannes Schindelin wrote: > > > > > > > > The need for

Re: [PATCH v2 0/7] Macros for Asciidoctor support

2017-01-25 Thread Jeff King
On Wed, Jan 25, 2017 at 11:19:26PM +, brian m. carlson wrote: > On Wed, Jan 25, 2017 at 04:35:44PM -0500, Jeff King wrote: > > On Wed, Jan 25, 2017 at 02:28:55PM +0100, Johannes Schindelin wrote: > > > > > > The need for the extensions could be replaced with a small amount of > > > > Ruby

Re: [PATCH v2 0/7] Macros for Asciidoctor support

2017-01-25 Thread brian m. carlson
On Wed, Jan 25, 2017 at 04:35:44PM -0500, Jeff King wrote: > On Wed, Jan 25, 2017 at 02:28:55PM +0100, Johannes Schindelin wrote: > > > > The need for the extensions could be replaced with a small amount of > > > Ruby code, if that's considered desirable. Previous opinions on doing > > > so were

Re: [PATCH v2 0/7] Macros for Asciidoctor support

2017-01-25 Thread Jeff King
On Wed, Jan 25, 2017 at 02:28:55PM +0100, Johannes Schindelin wrote: > > The need for the extensions could be replaced with a small amount of > > Ruby code, if that's considered desirable. Previous opinions on doing > > so were negative, however. > > Quite frankly, it is annoying to be forced

Re: [PATCH v2 0/7] Macros for Asciidoctor support

2017-01-25 Thread Johannes Schindelin
Hi Brian, On Sun, 22 Jan 2017, brian m. carlson wrote: > There are two major processors of AsciiDoc: AsciiDoc itself, and > Asciidoctor. Both have advantages and disadvantages, but traditionally > the documentation has been built with AsciiDoc, leading to some > surprising breakage when

Re: [PATCH v2 0/7] Macros for Asciidoctor support

2017-01-23 Thread Junio C Hamano
"brian m. carlson" writes: > There are two major processors of AsciiDoc: AsciiDoc itself, and Asciidoctor. > Both have advantages and disadvantages, but traditionally the documentation > has > been built with AsciiDoc, leading to some surprising breakage when

[PATCH v2 0/7] Macros for Asciidoctor support

2017-01-21 Thread brian m. carlson
There are two major processors of AsciiDoc: AsciiDoc itself, and Asciidoctor. Both have advantages and disadvantages, but traditionally the documentation has been built with AsciiDoc, leading to some surprising breakage when building with Asciidoctor. Partially, this is due to the need to specify