From: "brian m. carlson"
This series is designed to implement the changes necessary to build
Git
using Asciidoctor instead of AsciiDoc.
[..]
Even with these patches, Asciidoctor warns about everyday.txt and
user-manual.txt. I'm not sending patches for these right now because
I've seen recent
On Wed, Oct 15, 2014 at 01:24:22PM +0200, Thomas Braun wrote:
> Am 14.10.2014 um 11:51 schrieb Jeff King:
> > What's the status on AsciiDoc versus AsciiDoctor? The latter seems more
> > actively developed these days, but perhaps that is just my perception.
> > The incompatibilities seem fairly mini
"brian m. carlson" writes:
> On Tue, Oct 14, 2014 at 10:08:19AM -0700, Junio C Hamano wrote:
>> Jeff King writes:
>>
>> > On Sat, Oct 11, 2014 at 11:37:32PM +, brian m. carlson wrote:
>> >
>> > Specifically I'm not excited about getting into a state where we have to
>> > maintain both an as
Am 14.10.2014 um 11:51 schrieb Jeff King:
> What's the status on AsciiDoc versus AsciiDoctor? The latter seems more
> actively developed these days, but perhaps that is just my perception.
> The incompatibilities seem fairly minimal (if those first two patches
> are the extent of it, I have no prob
On Tue, Oct 14, 2014 at 10:08:19AM -0700, Junio C Hamano wrote:
> Jeff King writes:
>
> > On Sat, Oct 11, 2014 at 11:37:32PM +, brian m. carlson wrote:
> >
> > Specifically I'm not excited about getting into a state where we have to
> > maintain both an asciidoc.conf file _and_ ruby extension
Jeff King writes:
> On Sat, Oct 11, 2014 at 11:37:32PM +, brian m. carlson wrote:
>
> Specifically I'm not excited about getting into a state where we have to
> maintain both an asciidoc.conf file _and_ ruby extensions for
> asciidoctor. I don't mind if somebody wants to step up and keep the
On Sat, Oct 11, 2014 at 11:37:32PM +, brian m. carlson wrote:
> This series is designed to implement the changes necessary to build Git
> using Asciidoctor instead of AsciiDoc.
Thanks. I had always taken the attitude that we wrote for the original
Python AsciiDoc, and that using AsciiDoctor w
On Tue, Oct 14, 2014 at 12:07:51PM +0200, Jakub Narębski wrote:
> brian m. carlson wrote:
> >On Mon, Oct 13, 2014 at 01:41:31PM -0700, Junio C Hamano wrote:
> >>
> >>What I do not understand is that 3/4 lets you drop inclusion of
> >>asciidoc.conf which contains a lot more than just linkgit:
> >>de
brian m. carlson wrote:
On Mon, Oct 13, 2014 at 01:41:31PM -0700, Junio C Hamano wrote:
"brian m. carlson" writes:
The second two patches implement some basic support for building with
Asciidoctor. The first of these moves some items into variables due to
some differences between the AsciiDo
On Mon, Oct 13, 2014 at 01:41:31PM -0700, Junio C Hamano wrote:
> "brian m. carlson" writes:
>
> > The second two patches implement some basic support for building with
> > Asciidoctor. The first of these moves some items into variables due to
> > some differences between the AsciiDoc and Asciid
"brian m. carlson" writes:
> This series is designed to implement the changes necessary to build Git
> using Asciidoctor instead of AsciiDoc.
>
> The first two patches are bug fixes. Asciidoctor is stricter about
> title underline lengths (± 1 character instead of 2) and requires
> matching deli
This series is designed to implement the changes necessary to build Git
using Asciidoctor instead of AsciiDoc.
The first two patches are bug fixes. Asciidoctor is stricter about
title underline lengths (± 1 character instead of 2) and requires
matching delimiter lengths[0]. They're needed regard
12 matches
Mail list logo
