On Fri, Sep 09, 2011 at 10:37:24AM -0700, Junio C Hamano wrote: > Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> writes: > > > Our own customisation is not loaded (of course) so that, e.g., the > > linkgit macro does not work; and the include statement makes GitHub's > > parser unhappy and choke. > > > > Does anybody feel this is worth pursuing? > > > > + Nicer blob view > > + Simpler way to judge documentation changes > > - Need to get our asciidoc config in there > > - GitHub's parser neeeds to learn include > > Personally I am not very interested. Couldn't you just visit the html > branch instead for viewing? I agree that it's not very nice for release-quality documentation. But if I understand correctly, Michael means that you can go straight to any blob at any commit of any fork on github, and get the rendered (or raw) version. Which is neat. How frequently do you build the html branch? I always assumed it was once in a while (every push?), not for every commit. We could help that along by giving our documentation a more descriptive filename. But it would be cool if GitHub respected gitattributes for this, too. -Peff -- 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