git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
	"Jakub Narębski" <jnareb@gmail.com>
Subject: Re: [PATCH v2 0/3] Allow building Git with Asciidoctor
Date: Mon, 20 Oct 2014 02:24:25 -0700	[thread overview]
Message-ID: <20141020092425.GD12913@peff.net> (raw)
In-Reply-To: <1413764438-297386-1-git-send-email-sandals@crustytoothpaste.net>

On Mon, Oct 20, 2014 at 12:20:35AM +0000, brian m. carlson wrote:

> This series is designed to implement the changes necessary to build Git
> using Asciidoctor instead of AsciiDoc.

These all looked sane to me from my cursory read (I haven't played with
AsciiDoctor myself yet, but it looks from your results like you have).

> I've successfully built the documentation with Asciidoctor using the
> following command line:
> 
>   make doc ASCIIDOC=asciidoctor ASCIIDOC_HTML=html5 \
>   ASCIIDOC_DOCBOOK=docbook45 ASCIIDOC_EXTRA="'-alitdd=&#45;&#45;'" \
>   ASCIIDOC_CONF=

That incantation is getting a bit hairy. Is it worth adding a meta-macro
like USE_ASCIIDOCTOR that encompasses it all? That might encourage other
people to play around with it.

-Peff

  parent reply	other threads:[~2014-10-20  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20  0:20 [PATCH v2 0/3] Allow building Git with Asciidoctor brian m. carlson
2014-10-20  0:20 ` [PATCH v2 1/3] Documentation: adjust document title underlining brian m. carlson
2014-10-20  0:20 ` [PATCH v2 2/3] Documentation: fix mismatched delimiters in git-imap-send brian m. carlson
2014-10-20  0:20 ` [PATCH v2 3/3] Documentation: move some AsciiDoc parameters into variables brian m. carlson
2014-10-20  9:24 ` Jeff King [this message]
2014-10-20 19:08 ` [PATCH v2 0/3] Allow building Git with Asciidoctor Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141020092425.GD12913@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).