git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/4] Allow building Git with Asciidoctor

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 15, 2014, 17:43 UTC
Message-ID
<xmqqsiipw7ne.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20141015011754.GA131351@vauxhall.crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
Show 18 quoted lines
> On Tue, Oct 14, 2014 at 10:08:19AM -0700, Junio C Hamano wrote:
>> Jeff King <peff@peff.net> 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".
>> 
>> 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.
>
> Alternately, I'm happy to be responsible for maintaining the
> extensions.rb file.

Let's see how well the patches 3 and 4 work for other people with AsciiDoctor and then decide to go in that direction.

I do not forsee that changes to allow our *.txt to be used with AsciiDoctor interfere with what GitHub folks do with their own documentation toolchain, but I am not sure how the AsciiDoctor specific alternative build infrastructure we would eventually ship would interact with them---maybe they are not affected at all, or maybe they can even take advantage of it.

Thanks.
Previous: brian m. carlsonNext: Thomas Braun
Message 16 of 19 in “Allow building Git with Asciidoctor”
  1. 0/4 Allow building Git with Asciidoctorbrian m. carlson, Oct 11, 2014
  2. 1/4 Documentation: adjust document title underliningbrian m. carlson, Oct 11, 2014
  3. Junio C HamanoOct 13, 2014
  4. 2/4 Documentation: fix mismatched delimiters in git-imap-sendbrian m. carlson, Oct 11, 2014
  5. 3/4 Documentation: move some AsciiDoc parameters into variablesbrian m. carlson, Oct 11, 2014
  6. Junio C HamanoOct 15, 2014
  7. brian m. carlsonOct 16, 2014
  8. 4/4 Documentation: implement linkgit macro for Asciidoctorbrian m. carlson, Oct 11, 2014
  9. Junio C HamanoOct 13, 2014
  10. brian m. carlsonOct 14, 2014
  11. Jakub NarębskiOct 14, 2014
  12. brian m. carlsonOct 14, 2014
  13. Jeff KingOct 14, 2014
  14. Junio C HamanoOct 14, 2014
  15. brian m. carlsonOct 15, 2014
  16. Junio C HamanoOct 15, 2014
  17. Thomas BraunOct 15, 2014
  18. brian m. carlsonOct 15, 2014
  19. Philip OakleyOct 16, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.