Re: RFD: leveraging GitHub's asciidoc rendering for our Documentation/

From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date: Sep 10, 2011, 03:02 UTC
Message-ID: <j4ek0n$fsi$1@dough.gmane.org>
In-Reply-To: <CAP2yMaJ+UBHZp0U=QWOZbnbbOuq8vNoJODWtxZPb1sKXTC_UEg@mail.gmail.com>

Scott Chacon wrote:

Show 11 quoted lines

> Hey,
> 
> On Fri, Sep 9, 2011 at 7:34 AM, Michael J Gruber
> <git@drmicha.warpmail.net> 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.

Rather than forcing a rename on the repository, do you think it would be possible to implement some form of gitattribute support in GitHub? The user could then specify something like render=asciidoc (as opposed to, say, render=markdown or render=rdoc or whatever else you support): a few simple additions to .gitattributes and the user would be able to customize the cooked file view without needing to use GitHub's expected extension.

-- 
Giuseppe Bilotta