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

Re: What's cooking in git.git (Mar 2012, #02; Sun, 4)

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 5, 2012, 23:17 UTC
Message-ID
<7vsjhmy6x2.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAFfmPPPa=s8NAYDxoSa5SR91Y_tgRLUVo_bzgViE0wV5g0Ld3g@mail.gmail.com>
David Barr <davidbarr@google.com> writes:
> GitHub has a different mechanism for publishing project content.
> They expect a special named branch, gh-pages.

Hrm, so if they add a mechanism to name what branch to show the content from, I could set it from gh-pages to master and we will have an online HTML pages. Nice.

I wonder if they can also do historical documents (e.g. manual pages for release 1.7.0) that way.

> I thought it might be of interest that both Google Code and GitHub
> provide git-friendly means of publishing project content.
Previous: David BarrNext: Scott Chacon
Message 5 of 7 in “What's cooking in git.git (Mar 2012, #02; Sun, 4)”
  1. Junio C HamanoMar 5, 2012
  2. David BarrMar 5, 2012
  3. Junio C HamanoMar 5, 2012
  4. David BarrMar 5, 2012
  5. Junio C HamanoMar 5, 2012
  6. Scott ChaconMar 5, 2012
  7. Junio C HamanoMar 5, 2012

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.