From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: broken git-fast-import.xml
Date: Thu, 8 Feb 2007 18:13:41 -0500 [thread overview]
Message-ID: <20070208231341.GB1382@spearce.org> (raw)
In-Reply-To: <864ppwtffu.fsf@blue.stonehenge.com>
"Randal L. Schwartz" <merlyn@stonehenge.com> wrote:
> xmlto -m callouts.xsl man git-fast-import.xml
> xmlto: input does not validate (status 1)
> /Volumes/UFS/MIRROR/git-GIT/Documentation/git-fast-import.xml:527: parser error : Opening and ending tag mismatch: superscript line 527 and literal
> <simpara>The <literal><superscript>0</literal> suffix is necessary as gfi does n
> ^
> /Volumes/UFS/MIRROR/git-GIT/Documentation/git-fast-import.xml:529: parser error : Opening and ending tag mismatch: literal line 529 and superscript
> m</literal> command is even read from the input. Adding <literal></superscript>
> ^
> make[1]: *** [git-fast-import.1] Error 1
> rm git-fast-import.xml git-diff-stages.xml
Thanks. I already knew about the problem and fixed it in 209f1298.
I think Junio planned on pulling this in from my branch on repo.or.cz:
git://repo.or.cz/git/fastimport
but it hasn't made it to kernel.org yet. Here's the patch, if you
want to apply it yourself:
--8>--
From: Shawn O. Pearce <spearce@spearce.org>
Date: Thu, 8 Feb 2007 01:35:37 -0500
Subject: [PATCH] Correct ^0 asciidoc syntax in fast-import docs.
I wrote this documentation with asciidoc 7.1.2, but apparently
asciidoc 8 assumes ^ means superscript. The solution was already
documented in rev-parse's manpage and is to use {caret} instead.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
---
Documentation/git-fast-import.txt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-fast-import.txt b/Documentation/git-fast-import.txt
index 0b64d33..0c44761 100644
--- a/Documentation/git-fast-import.txt
+++ b/Documentation/git-fast-import.txt
@@ -380,9 +380,9 @@ current branch value should be written as:
----
from refs/heads/branch^0
----
-The `^0` suffix is necessary as gfi does not permit a branch to
+The `{caret}0` suffix is necessary as gfi does not permit a branch to
start from itself, and the branch is created in memory before the
-`from` command is even read from the input. Adding `^0` will force
+`from` command is even read from the input. Adding `{caret}0` will force
gfi to resolve the commit through Git's revision parsing library,
rather than its internal branch table, thereby loading in the
existing value of the branch.
--
1.5.0.rc4
prev parent reply other threads:[~2007-02-08 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 23:09 broken git-fast-import.xml Randal L. Schwartz
2007-02-08 23:13 ` Shawn O. Pearce [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070208231341.GB1382@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
/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).