public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox•net>
To: hanwen@xs4all•nl
Cc: git@vger•kernel.org
Subject: Re: doc bug?
Date: Sat, 09 Dec 2006 10:42:32 -0800	[thread overview]
Message-ID: <7vslfodi7b.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <elc64k$t4i$1@sea.gmane.org> (Han-Wen Nienhuys's message of "Fri, 08 Dec 2006 18:07:43 +0100")

Han-Wen Nienhuys <hanwen@xs4all•nl> writes:

> 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:

That is interesting.  git-tools is listed on ARTICLES which is
excluded from MAN1_TXT so the Makefile should not even try to
run the above commandline that says 'manpage'.

At least that is what our Makefile intends to do.

So that means you may have found a bug in our Makefile, or your
make (by the way I think we pretty much requires GNU make to
build git), or perhaps both.

But I do not see an obvious breakage in our Makefile in this
area...



  parent reply	other threads:[~2006-12-09 18:42 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
2006-12-09 18:04   ` Han-Wen Nienhuys
2006-12-09 18:42 ` Junio C Hamano [this message]
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=7vslfodi7b.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=hanwen@xs4all$(echo .)nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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