From: hesco@greens.org (Hugh Esco)
To: gitster@pobox.com, peff@peff.net
Cc: git@vger.kernel.org, hesco@yourmessagedelivered.com
Subject: Re: bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130: parser error
Date: Sun, 30 Sep 2012 11:29:39 -0700 (PDT) [thread overview]
Message-ID: <20120930182939.30C058059E@mail.greens.org> (raw)
In-Reply-To: <20120930180209.GA13596@sigill.intra.peff.net>
Your are correct. That is apparently the issue:
git@pbx:~$ asciidoc --version
asciidoc 8.2.7
This server is still running Debian Lenny.
Not sure when I will be able to rebuild it.
My apologies for spamming your bug reporting list
with all of that. I now have source installs of git
and gitolite installed and presumably working on this
server and promise not to bother you further with
that issue.
-- Hugh Esco
Date: Sun, 30 Sep 2012 14:02:09 -0400
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: hesco@yourmessagedelivered.com, git@vger.kernel.org
Subject: Re: bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130:
parser error
On Sun, Sep 30, 2012 at 12:34:18AM -0700, Junio C Hamano wrote:
> I suspect that a tilde inside literal `` environment is mishandled
> in your versions of the documentation toolchain. Either you would
> need to upgrade some tool in the toolchain, or we would need patches
> to the source that would look like:
>
> -such as `master~1` cannot be packaged,...
> +such as `master{tilde}1` cannot be packaged,...
>
> to work around this problem if the version of the problematic tool
> you are using is widespread.
That would not work, as commit 6cf378f turned off no-inline-literal, and
modern asciidoc would not expand that "{tilde}" at all. My guess is that
Hugh is using a version of asciidoc older than 8.4.1, which was the
first version to understand inline literals.
This came up already once before:
http://thread.gmane.org/gmane.comp.version-control.git/198733
where the culprit was older third-party RPMs on RHEL5. It can be worked
around by upgrading asciidoc, or using "make quick-install-doc" to pull
the pre-built versions.
-Peff
prev parent reply other threads:[~2012-09-30 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 7:08 bug report, v1.7.12.1 -- Documentation/git-bundle.xml:130: parser error Hugh Esco
2012-09-30 7:34 ` Junio C Hamano
2012-09-30 18:02 ` Jeff King
2012-09-30 18:29 ` Hugh Esco [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120930182939.30C058059E@mail.greens.org \
--to=hesco@greens.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hesco@campaignfoundations.com \
--cc=hesco@yourmessagedelivered.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).