* how to patch git documentation
@ 2012-03-09 2:38 Neal Kreitzinger
2012-03-09 2:43 ` Junio C Hamano
0 siblings, 1 reply; 5+ messages in thread
From: Neal Kreitzinger @ 2012-03-09 2:38 UTC (permalink / raw)
To: git
Is there a document on how to patch git documentation?
Basic question:
What language are the git documentation *.txt files written in?
v/r,
neal
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: how to patch git documentation
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 23:11 ` Neal Kreitzinger
0 siblings, 2 replies; 5+ messages in thread
From: Junio C Hamano @ 2012-03-09 2:43 UTC (permalink / raw)
To: Neal Kreitzinger; +Cc: git
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 ;-).
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: how to patch git documentation
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
1 sibling, 1 reply; 5+ messages in thread
From: Neal Kreitzinger @ 2012-03-09 5:15 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
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 ;-).
>
Is it ok to submit patches to git.git using msysgit, and also from
git-osx? I'm not sure how fast I can get past our security people on
the linux servers, if at all.
v/r,
neal
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: how to patch git documentation
2012-03-09 5:15 ` Neal Kreitzinger
@ 2012-03-09 5:49 ` Junio C Hamano
0 siblings, 0 replies; 5+ messages in thread
From: Junio C Hamano @ 2012-03-09 5:49 UTC (permalink / raw)
To: Neal Kreitzinger; +Cc: git
Neal Kreitzinger <nkreitzinger@gmail.com> writes:
> 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 ;-).
>>
> Is it ok to submit patches to git.git using msysgit, and also from
> git-osx? I'm not sure how fast I can get past our security people on
> the linux servers, if at all.
Honestly, I highly doubt if I could even tell if your patch was
created with "git format-patch" running on Linux, Mac OS X, Windows,
or CP/M-86 for that matter. As long as the port of Git to the
platform is working correctly, that is.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: how to patch git documentation
2012-03-09 2:43 ` Junio C Hamano
2012-03-09 5:15 ` Neal Kreitzinger
@ 2012-03-09 23:11 ` Neal Kreitzinger
1 sibling, 0 replies; 5+ messages in thread
From: Neal Kreitzinger @ 2012-03-09 23:11 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-03-09 23:11 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).