From: Pascal Obry <pascal@obry.net>
To: git list <git@vger.kernel.org>
Subject: Git doc generation question
Date: Fri, 19 Nov 2010 17:26:34 +0100 [thread overview]
Message-ID: <4CE6A53A.9090203@obry.net> (raw)
Hi,
I'm building Git from source and in the documentation I have some code
remaining, for example:
$ man git
git me in the CONFIGURATION MECHANISM section:
<<
example:
.ft C
#
# A '#' or ';' character indicates a comment.
#
; core variables
...
.ft
>>
It looks like the ".ft C" and the ending .ft are some code not properly
parsed. Right?
Is that a known issue?
I had this problem on Cygwin and now on GNU/Debian!
Thanks,
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net - http://v2p.fr.eu.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver keys.gnupg.net --recv-key F949BD3B
next reply other threads:[~2010-11-19 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 16:26 Pascal Obry [this message]
2010-11-19 16:47 ` Git doc generation question Drew Northup
2010-11-19 17:02 ` Pascal Obry
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=4CE6A53A.9090203@obry.net \
--to=pascal@obry.net \
--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).