Re: Git doc generation question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2010-11-19 at 17:26 +0100, Pascal Obry wrote:
> 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,
Have a look at this thread:
http://article.gmane.org/gmane.comp.version-control.git/161607


-- 
-Drew Northup N1XIM
   AKA RvnPhnx on OPN
________________________________________________
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]