git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Warnings from asciidoc (in parallel compilation?)
Date: Mon, 21 Mar 2011 09:24:16 +0100	[thread overview]
Message-ID: <AANLkTikY+dWX-=ci8_hG6e5RNW-0sZ30R-2G7YUEWVv8@mail.gmail.com> (raw)

Hi,

I'm compiling master and I'm getting some warnings from documentation.
Some might be connected with parallel compilation - for example
Documentation/cmds-* are autogenerated.

My command line was:
make -j3 prefix=/usr/local/stow/git-master all doc info

[...]
    ASCIIDOC gitk.html
    ASCIIDOC git.html
    ASCIIDOC git-svn.xml
asciidoc: WARNING: git.txt: line 350: include file not found:
/usr/local/src/git/git/Documentation/cmds-mainporcelain.txt
asciidoc: WARNING: git.txt: line 356: include file not found:
/usr/local/src/git/git/Documentation/cmds-ancillarymanipulators.txt
    ASCIIDOC git-symbolic-ref.xml
asciidoc: WARNING: git.txt: line 360: include file not found:
/usr/local/src/git/git/Documentation/cmds-ancillaryinterrogators.txt
asciidoc: WARNING: git.txt: line 369: include file not found:
/usr/local/src/git/git/Documentation/cmds-foreignscminterface.txt
asciidoc: WARNING: git.txt: line 398: include file not found:
/usr/local/src/git/git/Documentation/cmds-plumbingmanipulators.txt
asciidoc: WARNING: git.txt: line 404: include file not found:
/usr/local/src/git/git/Documentation/cmds-plumbinginterrogators.txt
asciidoc: WARNING: git.txt: line 413: include file not found:
/usr/local/src/git/git/Documentation/cmds-synchingrepositories.txt
asciidoc: WARNING: git.txt: line 418: include file not found:
/usr/local/src/git/git/Documentation/cmds-synchelpers.txt
asciidoc: WARNING: git.txt: line 427: include file not found:
/usr/local/src/git/git/Documentation/cmds-purehelpers.txt
    LINK test-genrandom
    ASCIIDOC gitattributes.html
[...]
    ASCIIDOC technical/api-diff.html
    ASCIIDOC technical/api-directory-listing.html
    LN/CP git-remote-ftps
    ASCIIDOC technical/api-gitattributes.html
    ASCIIDOC git.xml
docbook2texi:/book: no description for directory entry
    ASCIIDOC technical/api-grep.html
    ASCIIDOC technical/api-hash.html
    ASCIIDOC technical/api-history-graph.html
[...]
    XMLTO git-daemon.1
    XMLTO git-describe.1
    XMLTO git-diff-files.1
    MAKEINFO gitman.info
gitman.texi:6910: warning: @strong{Note...} produces a spurious
cross-reference in Info; reword to avoid that.
gitman.texi:26398: warning: @strong{Note...} produces a spurious
cross-reference in Info; reword to avoid that.
make[1]: Leaving directory `/usr/local/src/git/git/Documentation'
    XMLTO git-diff-index.1
    XMLTO git-difftool.1
    XMLTO git-diff-tree.1
[...]
    XMLTO git-name-rev.1
    XMLTO git-notes.1
    XMLTO git-pack-objects.1
Warn: endnote  #1 : Bad: footnote[1] in source                     git-notes
Note: endnote  #1 : Has: footnote/simpara                          git-notes
Note: endnote  #1 : Fix: footnote/para/simpara                     git-notes
    XMLTO git-pack-redundant.1
    XMLTO git-pack-refs.1
    XMLTO git-parse-remote.1


-- 
Piotr Krukowiecki

                 reply	other threads:[~2011-03-21  8:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='AANLkTikY+dWX-=ci8_hG6e5RNW-0sZ30R-2G7YUEWVv8@mail.gmail.com' \
    --to=piotr.krukowiecki@gmail.com \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).