From: Martin Waitz <tali@admingilde.org>
To: Jeff King <peff@peff.net>
Cc: Scott Lamb <slamb@slamb.org>, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, jonas.fonseca@gmail.com
Subject: Re: [PATCH] catch asciidoc failures
Date: Fri, 1 Jun 2007 11:39:29 +0200 [thread overview]
Message-ID: <20070601093929.GC3521@admingilde.org> (raw)
In-Reply-To: <20070601091030.GA2215@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
hoi :)
On Fri, Jun 01, 2007 at 05:10:30AM -0400, Jeff King wrote:
> As Jonas suggested, making it an asciidoc attribute is much more
> elegant (patch even tested!):
very nice!
Does that need any special asciidoc version?
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-01 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 6:23 [PATCH] catch asciidoc failures Scott Lamb
2007-06-01 8:36 ` Martin Waitz
2007-06-01 8:55 ` Jonas Fonseca
2007-06-01 9:10 ` Jeff King
2007-06-01 9:39 ` Martin Waitz [this message]
2007-06-01 9:43 ` Jeff King
2007-06-01 9:46 ` Scott Lamb
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=20070601093929.GC3521@admingilde.org \
--to=tali@admingilde.org \
--cc=git@vger.kernel.org \
--cc=jonas.fonseca@gmail.com \
--cc=junkio@cox.net \
--cc=peff@peff.net \
--cc=slamb@slamb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox