From: Michael Haggerty Date: Fri, 09 Sep 2011 15:58:06 GMT Subject: Re: RFD: leveraging GitHub's asciidoc rendering for our Documentation/ Message-ID: <4E6A378E.6020704@alum.mit.edu> In-Reply-To: On 09/09/2011 05:45 PM, Scott Chacon wrote: > On Fri, Sep 9, 2011 at 7:34 AM, Michael J Gruber > wrote: >> which has all the renaming (*.txt -> *.asciidoc) and Makefile and script >> changes, but is missing some include changes (because include breaks >> anyway, see below). > > I can change this so we can render .asc if that's less ugly. I've > been meaning to do this for a while, but I don't think I ever > incorporated it. What about letting the project set a gitattribute that tells github how to render particular files? It would not require files to be renamed, and it would be more flexible. OTOH it would not be possible to apply gitattributes (or file renamings) to old revisions, so the history would continue to be rendered naively. But here's an additional idea: github could provide web access to the equivalent of $GIT_DIR/info/attributes (a project-wide .gitattributes file), which would allow the rendering of files in historical revisions to be customized and would also allow github rendering behavior to be defined even in projects that do not want github-specific tags in the .gitattributes files in their project. Michael -- Michael Haggerty mhagger@alum.mit.edu http://softwareswirl.blogspot.com/