From: Steven Grimm <koreth@midwinter.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ismail Dönmez" <ismail@pardus.org.tr>,
git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.3-rc4
Date: Sat, 04 Aug 2007 18:55:26 +0800 [thread overview]
Message-ID: <46B45B1E.5020104@midwinter.com> (raw)
In-Reply-To: <20070804091249.GA17821@uranus.ravnborg.org>
Sam Ravnborg wrote:
> Never looked at Ascii-doc... but how about finding the loopholes
> in Ascii-doc to make it 10x faster?
> That would benefit a larger user-base than just doing-it-ourself.
>
Because AsciiDoc is only half of the toolchain we use. (Though in your
defense, I made the mistake of only mentioning AsciiDoc by name, rather
than "the AsciiDoc toolchain.") We run asciidoc's output through xmlto,
which is just as slow and is a highly general piece of software for
doing arbitrary transformations of XML documents. I won't say it's
impossible to speed up xmlto as well, of course, but it's probably an
order of magnitude more work than implementing a new parser/renderer for
our .txt files.
-Steve
next prev parent reply other threads:[~2007-08-04 10:55 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 0:28 [ANNOUNCE] GIT 1.5.3-rc4 Junio C Hamano
2007-08-04 0:41 ` Ismail Dönmez
2007-08-04 1:30 ` Junio C Hamano
2007-08-04 1:48 ` Ismail Dönmez
2007-08-04 3:13 ` Junio C Hamano
2007-08-04 13:26 ` Ismail Dönmez
2007-08-04 3:49 ` Steven Grimm
2007-08-04 4:38 ` Junio C Hamano
2007-08-04 4:57 ` Daniel Barkalow
2007-08-04 5:23 ` Junio C Hamano
2007-08-04 5:52 ` Daniel Barkalow
2007-08-04 6:11 ` Steven Grimm
2007-08-04 6:17 ` Doug Maxey
2007-08-04 9:12 ` Sam Ravnborg
2007-08-04 10:55 ` Steven Grimm [this message]
2007-08-04 12:19 ` David Kastrup
2007-08-04 16:03 ` Steven Grimm
2007-08-04 16:08 ` Johannes Schindelin
2007-08-04 16:27 ` David Kastrup
2007-08-05 9:50 ` Jeff King
2007-08-04 16:59 ` Linus Torvalds
2007-08-04 17:49 ` David Kastrup
2007-08-04 19:03 ` Linus Torvalds
2007-08-04 19:55 ` David Kastrup
2007-08-04 21:27 ` J. Bruce Fields
2007-08-05 4:29 ` Linus Torvalds
2007-08-05 7:51 ` David Kastrup
2007-08-05 17:08 ` Linus Torvalds
2007-08-05 18:08 ` David Kastrup
2007-08-05 18:23 ` Linus Torvalds
2007-08-05 18:35 ` Johannes Schindelin
2007-08-05 19:11 ` David Kastrup
2007-08-05 19:06 ` David Kastrup
2007-08-05 20:32 ` David Kastrup
2007-08-05 19:29 ` Linus Torvalds
2007-08-05 21:43 ` Bruce Korb
2007-08-05 22:15 ` David Kastrup
2007-08-05 22:31 ` J. Bruce Fields
2007-08-08 8:11 ` Man-pages in user manual (was: [ANNOUNCE] GIT 1.5.3-rc4) David Kastrup
2007-08-05 23:38 ` [ANNOUNCE] GIT 1.5.3-rc4 Junio C Hamano
2007-08-06 0:13 ` Miles Bader
2007-08-06 5:44 ` David Kastrup
2007-08-05 9:42 ` Jeff King
2007-08-05 9:54 ` David Kastrup
2007-08-05 9:59 ` Jeff King
2007-08-05 10:20 ` David Kastrup
2007-08-05 10:22 ` Jeff King
2007-08-05 10:40 ` David Kastrup
2007-08-05 11:23 ` David Kastrup
2007-08-04 11:38 ` Johannes Schindelin
2007-08-04 14:29 ` J. Bruce Fields
2007-08-04 7:30 ` David Kastrup
2007-08-04 10:39 ` Timo Hirvonen
2007-08-04 11:46 ` Johannes Schindelin
2007-08-04 12:51 ` Timo Hirvonen
2007-08-04 15:19 ` Michael
2007-08-04 13:11 ` Robin Rosenberg
2007-08-04 13:42 ` Julian Phillips
2007-08-07 12:11 ` David Kågedal
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=46B45B1E.5020104@midwinter.com \
--to=koreth@midwinter.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ismail@pardus.org.tr \
--cc=sam@ravnborg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.