From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
Subject: Re: RFD: leveraging GitHub's asciidoc rendering for our Documentation/
Date: Sat, 10 Sep 2011 05:02:44 +0200 [thread overview]
Message-ID: <j4ek0n$fsi$1@dough.gmane.org> (raw)
In-Reply-To: CAP2yMaJ+UBHZp0U=QWOZbnbbOuq8vNoJODWtxZPb1sKXTC_UEg@mail.gmail.com
Scott Chacon wrote:
> 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
next prev parent reply other threads:[~2011-09-10 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 14:34 RFD: leveraging GitHub's asciidoc rendering for our Documentation/ Michael J Gruber
2011-09-09 15:45 ` Scott Chacon
2011-09-09 15:58 ` Michael Haggerty
2011-09-09 16:05 ` Michael J Gruber
2011-09-10 3:02 ` Giuseppe Bilotta [this message]
[not found] ` <CAMK1S_hOY-riZnHAZhC32UAA0BYF1YyXUPujj_jFUEjcYC_4ZA@mail.gmail.com>
2011-09-09 15:55 ` Fwd: " Sitaram Chamarty
2011-09-09 17:37 ` Junio C Hamano
2011-09-09 19:05 ` Michael J Gruber
2011-09-09 19:05 ` Jeff King
2011-09-09 20:50 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='j4ek0n$fsi$1@dough.gmane.org' \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).