Scott Chacon <schacon@xxxxxxxxx> writes: > Hey, > > On Mon, Mar 5, 2012 at 3:17 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> David Barr <davidbarr@xxxxxxxxxx> 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. I do not mind pushing to gh-pages branch but I just wanted to avoid an extra branch appearing in the repository where people expect to find "master" branch full of html pages, which would surprise the users. > 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. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html