Junio C Hamano venit, vidit, dixit 09.09.2011 19:37: > 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? For viewing what you generated yes, of course. Though there's some fiddling if you want to view a specific version. And even for the latest version it is more direct to click on the file in the tree and see it rendered. But what I had in mind was being able to view anyone's branches like that, to aid review of a patch which is on list and in a branch on GitHub, say for restructuring layout or presentation of some man pages. The linkgit and include issues are a bit of a showstopper (looks like lots of digging in foreign code). Michael -- 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