# how to patch git documentation 5 messages from 2012-03-09 to 2012-03-09. Participants: Neal Kreitzinger, Junio C Hamano. Thread: https://gitlist.dev/t/29892 ## Neal Kreitzinger, 2012-03-09 02:38 Subject: how to patch git documentation Message-ID: URL: https://gitlist.dev/e/jjbqe9%248l3%241%40dough.gmane.org ``` 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 ``` ## Junio C Hamano, 2012-03-09 02:43 Subject: Re: how to patch git documentation Message-ID: <7v1up2bikm.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7v1up2bikm.fsf%40alter.siamese.dyndns.org In-Reply-To: ``` Neal Kreitzinger writes: > What language are the git documentation *.txt files written in? Mixture of Pidgin English and a bit of AsciiDoc ;-). ``` ## Neal Kreitzinger, 2012-03-09 05:15 Subject: Re: how to patch git documentation Message-ID: <4F5991D8.60207@gmail.com> URL: https://gitlist.dev/e/4F5991D8.60207%40gmail.com In-Reply-To: <7v1up2bikm.fsf@alter.siamese.dyndns.org> ``` On 3/8/2012 8:43 PM, Junio C Hamano wrote: > Neal Kreitzinger 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 ``` ## Junio C Hamano, 2012-03-09 05:49 Subject: Re: how to patch git documentation Message-ID: <7vk42u9ve2.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vk42u9ve2.fsf%40alter.siamese.dyndns.org In-Reply-To: <4F5991D8.60207@gmail.com> ``` Neal Kreitzinger writes: > On 3/8/2012 8:43 PM, Junio C Hamano wrote: >> Neal Kreitzinger 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. ``` ## Neal Kreitzinger, 2012-03-09 23:11 Subject: Re: how to patch git documentation Message-ID: <4F5A8E0C.20404@gmail.com> URL: https://gitlist.dev/e/4F5A8E0C.20404%40gmail.com In-Reply-To: <7v1up2bikm.fsf@alter.siamese.dyndns.org> ``` On 3/8/2012 8:43 PM, Junio C Hamano wrote: > Neal Kreitzinger 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 ```