From: "Jonas Fonseca" <jonas.fonseca@gmail.com>
To: hanwen@xs4all.nl
Cc: git@vger.kernel.org
Subject: Re: doc bug?
Date: Sat, 9 Dec 2006 18:30:08 +0100 [thread overview]
Message-ID: <2c6b72b30612090930o7b856223ub87746181f958b7c@mail.gmail.com> (raw)
In-Reply-To: <elc64k$t4i$1@sea.gmane.org>
On 12/8/06, Han-Wen Nienhuys <hanwen@xs4all.nl> wrote:
> Hi,
Hello,
> while messing with GIT's build system, I got
>
> **
> asciidoc -b docbook -d manpage -f ../Documentation/asciidoc.conf ../Documentation/git-tools.txt
> ERROR: git-tools.txt: line 2: malformed manpage title
> ERROR: git-tools.txt: line 6: first section must be named NAME
> ERROR: git-tools.txt: line 9: malformed NAME section body
> FAILED: /home/lilydev/vc/git/Documentation/git-tools.txt: line 9: unexpected error:
> [traceback]
> **
>
> is this a new problem? I'm on FC6, with asciidoc 7.0.2
The git-tools.txt document is not intended to be a man page
(there is no git-tools command) so it cannot be converted into
a man page. You should be able to make a HTML document
out of it, although the AsciiDoc formatting is not "optimal".
--
next prev parent reply other threads:[~2006-12-09 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 17:07 doc bug? Han-Wen Nienhuys
2006-12-09 17:30 ` Jonas Fonseca [this message]
2006-12-09 18:04 ` Han-Wen Nienhuys
2006-12-09 18:42 ` Junio C Hamano
2006-12-11 13:54 ` Han-Wen Nienhuys
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=2c6b72b30612090930o7b856223ub87746181f958b7c@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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).