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

Re: RFD: leveraging GitHub's asciidoc rendering for our Documentation/

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 9, 2011, 20:50 UTC
Message-ID
<7vehzptp88.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110909190547.GF28480@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> How frequently do you build the html branch? I always assumed it was
> once in a while (every push?), not for every commit.
I don't ;-)

Every time "master" is updated to the official distribution point, i.e., kernel.org (which currently is down). A post-update hook runs there, fetches the "master" branch commit into a separate repository, rebuilds the documentation, updates "html" and "man" branches and pushes the results back to that distribution point repository.

The mirrors will pick the result up after all that happens (or they may lag but they will eventually catch up).

Previous: Jeff KingNext: Sitaram Chamarty
Message 9 of 10 in “RFD: leveraging GitHub's asciidoc rendering for our Documentation/”
  1. Michael J GruberSep 9, 2011
  2. Scott ChaconSep 9, 2011
  3. Michael HaggertySep 9, 2011
  4. Michael J GruberSep 9, 2011
  5. Giuseppe BilottaSep 10, 2011
  6. Junio C HamanoSep 9, 2011
  7. Michael J GruberSep 9, 2011
  8. Jeff KingSep 9, 2011
  9. Junio C HamanoSep 9, 2011
  10. Fwd: RFD: leveraging GitHub's asciidoc rendering for our Documentation/Sitaram Chamarty, Sep 9, 2011

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.