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

Re: Git and Documentation

From
Michael Witten <mfwitten@gmail.com>
Date
Aug 10, 2010, 20:47 UTC
Message-ID
<AANLkTimK_ounhk1Qou02V_3+JjpY9Y5ZO3OO2uRn6A7k@mail.gmail.com>
In-Reply-To
<4C61B737.50108@dbservice.com>
On Tue, Aug 10, 2010 at 15:31, Tomas Carnecky <tom@dbservice.com> wrote:
> If the documentation is generated as part of the build, then there is no
> reason to have it part of the history - you can always rebuild it from
> the source. For the same reason you don't put compiled source into git.
Well, theoretically.
According to:
  http://git.kernel.org/?p=git/git.git;a=blob_plain;f=MaintNotes;hb=todo

the git project's repository itself tracks generated documentation for practical reasons:

  The "html" and "man" [branches] are
  autogenerated documentation from the
  tip of the "master" branch; the tip
  of "html" is extracted to be visible
  at kernel.org at:
    http://www.kernel.org/pub/software/scm/git/docs/
Previous: Tomas CarneckyNext: Michael Witten
Message 5 of 7 in “Git and Documentation”
  1. Sultan ShakirAug 9, 2010
  2. Ævar Arnfjörð BjarmasonAug 9, 2010
  3. Sultan ShakirAug 10, 2010
  4. Tomas CarneckyAug 10, 2010
  5. Michael WittenAug 10, 2010
  6. Michael WittenAug 10, 2010
  7. Sultan ShakirAug 11, 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.