git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git doc generation question

From
Drew Northup <drew.northup@maine.edu>
Date
Nov 19, 2010, 16:47 UTC
Message-ID
<1290185252.13785.1.camel@drew-northup.unet.maine.edu>
In-Reply-To
<4CE6A53A.9090203@obry.net>
On Fri, 2010-11-19 at 17:26 +0100, Pascal Obry wrote:
Show 32 quoted lines
> 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
Previous: Pascal ObryNext: Pascal Obry
Message 2 of 3 in “Git doc generation question”
  1. Pascal ObryNov 19, 2010
  2. Drew NorthupNov 19, 2010
  3. Pascal ObryNov 19, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.