From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: how to patch git documentation
Date: Fri, 09 Mar 2012 17:11:08 -0600 [thread overview]
Message-ID: <4F5A8E0C.20404@gmail.com> (raw)
In-Reply-To: <7v1up2bikm.fsf@alter.siamese.dyndns.org>
On 3/8/2012 8:43 PM, Junio C Hamano wrote:
> Neal Kreitzinger<nkreitzinger@gmail.com> writes:
>
>> What language are the git documentation *.txt files written in?
> Mixture of Pidgin English and a bit of AsciiDoc ;-).
>
>
Does someone have documentation on how to test the AsciiDoc changes of
their Documentation/ patches? This tester I found doesn't work right
because it not only shows my asciidoc changes misformatted in html, but
it also shows the original working asciidoc code from git.git as being
misformatted in html : http://andrewk.webfactional.com/asciidoc.php
v/r,
neal
prev parent reply other threads:[~2012-03-09 23:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 2:38 how to patch git documentation Neal Kreitzinger
2012-03-09 2:43 ` Junio C Hamano
2012-03-09 5:15 ` Neal Kreitzinger
2012-03-09 5:49 ` Junio C Hamano
2012-03-09 23:11 ` Neal Kreitzinger [this message]
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=4F5A8E0C.20404@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).