From: Jakub Narebski <jnareb@gmail.com>
To: Howard Miller <howard@e-learndesign.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Gitolite documentation mkd files??
Date: Sat, 12 Mar 2011 03:05:53 -0800 (PST) [thread overview]
Message-ID: <m3y64k61lt.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimQOzw-TYPO9ue3D_a0J8toFQZR4GDgoc2n2iin@mail.gmail.com>
Howard Miller <howard@e-learndesign.co.uk> writes:
> I'm sorry if this is the wrong place to ask...
>
> What's the story with '.mkd' files in which the docs are written for
> Gitolite? I would normally just check Google, but that doesn't seem to
> have heard of them either. What is there that reads them properly?
> It's only a minor inconvenience but I'm really just interested to
> know.
Those are files in Markdown[1] format, a lightweight document markup
language. GitHub renders it to HTML automatically. It is supposed to
be readable also in un-formatted form.
[1]: http://en.wikipedia.org/wiki/Markdown
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2011-03-12 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 9:32 Gitolite documentation mkd files?? Howard Miller
2011-03-12 11:05 ` Jakub Narebski [this message]
2011-03-12 11:21 ` Howard Miller
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=m3y64k61lt.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=howard@e-learndesign.co.uk \
/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