From: Scott Chacon <schacon@gmail.com>
Date: Mon, 05 Mar 2012 23:30:50 GMT
Subject: Re: What's cooking in git.git (Mar 2012, #02; Sun, 4)
Message-ID: <CAP2yMa+GgRV3W7FcRhVrpRTRfWrDxKhWgbkWVdzCyyN-zgcifA@mail.gmail.com>
In-Reply-To: <7vsjhmy6x2.fsf@alter.siamese.dyndns.org>

Hey,

On Mon, Mar 5, 2012 at 3:17 PM, Junio C Hamano <gitster@pobox.com> wrote:
> 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.

So, gh-pages is how you can publish project pages for a project.  If
you don't want to push to the gh-pages branch, you can just name the
repository 'gitster.github.com' and push to the master branch there
and that static content will be available at that url.

It just serves static content, so we won't serve older content automatically.

I am also working on parsing the content automatically and hosting it,
including all older versions, under the git-scm.com domain. - also
making it searchable and whatnot, FYI.  This won't be done for a
little while, but I am working on it.

Scott