From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Thomas Rast" <trast@inf.ethz.ch>,
"Junio C Hamano" <gitster@pobox.com>,
"Carlos Martín Nieto" <cmn@elego.de>,
"Matthieu Moy" <Matthieu.Moy@imag.fr>
Subject: [PATCH 0/3] docs: asciidoc version tweaks
Date: Wed, 30 May 2012 06:17:58 -0400 [thread overview]
Message-ID: <20120530101758.GA13285@sigill.intra.peff.net> (raw)
In-Reply-To: <20120529215613.GB17598@sigill.intra.peff.net>
On Tue, May 29, 2012 at 05:56:13PM -0400, Jeff King wrote:
> > > The commit message of 6cf378f0 is not correct in that respect. My
> > > ancient 71c020c5 has the right numbers: asciidoc 8.4.1 is the one that
> > > introduced the new inline-literal behavior. Based on my little survey
> > > in
>
> Yeah, sorry, this is my fault. It came up in discussion but I never
> amended the commit message. The magic number is definitely 8.4.1.
I think 6cf378f0 left a few other loose ends, too. Fixes to follow.
[1/3]: INSTALL: update asciidoc recommendation
[2/3]: docs: drop asciidoc7compatible flag
[3/3]: docs: drop antique comment from Makefile
-Peff
next prev parent reply other threads:[~2012-05-30 10:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 10:19 "docs: stop using asciidoc no-inline-literal" breaks asciidoc 8.2.5 Ævar Arnfjörð Bjarmason
2012-05-29 12:03 ` Thomas Rast
2012-05-29 12:31 ` Ævar Arnfjörð Bjarmason
2012-05-29 19:45 ` Junio C Hamano
2012-05-29 22:01 ` Jeff King
2012-05-29 21:56 ` Jeff King
2012-05-29 22:05 ` Dennis Kaarsemaker
2012-05-29 22:42 ` Ævar Arnfjörð Bjarmason
2012-05-29 22:51 ` Ævar Arnfjörð Bjarmason
2012-05-30 8:51 ` Jeff King
2012-05-30 9:02 ` Matthieu Moy
2012-05-30 10:17 ` Jeff King [this message]
2012-05-30 10:18 ` [PATCH 1/3] INSTALL: update asciidoc recommendation Jeff King
2012-05-30 10:22 ` [PATCH 2/3] docs: drop asciidoc7compatible flag Jeff King
2012-05-30 10:22 ` [PATCH 3/3] docs: drop antique comment from Makefile Jeff King
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=20120530101758.GA13285@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@imag.fr \
--cc=avarab@gmail.com \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@inf.ethz.ch \
/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).