Jeff King [off-list ref] writes:
On Sat, Oct 11, 2014 at 11:37:32PM +0000, 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
asciidoctor bits in sync with the asciidoc.conf, but I feel like one of
them needs to be considered the "master".
My so-far-unstated inclination, since seeing the patch to fix the
unbalanced example block separators from Brian (which was outside
and before this four-patch series), has been to keep our Makefile in
Documentation/ aware only of AsciiDoc while maintaining *.txt files
in a state so that AsciiDoctor could also be used to process them,
if people want to futz with their copies of Documentation/Makefile.
I do not mind to have the machinery to run AsciiDoctor too much in
my tree. It may make it easier for those who use it to spot places
in *.txt that need (in)compatibility workarounds between the two
formatters than keeping it outside.
But somebody needs to maintain that machinery and that will not be
me.
Thanks.
On Tue, Oct 14, 2014 at 10:08:19AM -0700, Junio C Hamano wrote:
Jeff King [off-list ref] writes:
quoted
On Sat, Oct 11, 2014 at 11:37:32PM +0000, 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
asciidoctor bits in sync with the asciidoc.conf, but I feel like one of
them needs to be considered the "master".
My so-far-unstated inclination, since seeing the patch to fix the
unbalanced example block separators from Brian (which was outside
and before this four-patch series), has been to keep our Makefile in
Documentation/ aware only of AsciiDoc while maintaining *.txt files
in a state so that AsciiDoctor could also be used to process them,
if people want to futz with their copies of Documentation/Makefile.
I do not mind to have the machinery to run AsciiDoctor too much in
my tree. It may make it easier for those who use it to spot places
in *.txt that need (in)compatibility workarounds between the two
formatters than keeping it outside.
I'd be happy if you simply picked up patch 3 and left out patch 4. It
gets us most of the way there, which is good enough for most things.
It's even possible to handle the litdd attribute on the command line, so
the only thing we'd really lose is the linkgit links.
Alternately, I'm happy to be responsible for maintaining the
extensions.rb file. The asciidoc.conf file has not had a substantive
(non-comment) change since 2012, and it has not had a change that would
require an update to the extensions since 2010. I don't anticipate that
keeping it up-to-date will require a significant amount of work. We can
even drop it into contrib if you think that's a better place.
It's really up to you which you'd prefer.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187