{"thread":{"id":"29892","subject":"how to patch git documentation","startedAt":"2012-03-09T02:38:01Z","lastAt":"2012-03-09T23:11:08Z","messageCount":5,"participants":["Neal Kreitzinger","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"186517","messageId":"jjbqe9$8l3$1@dough.gmane.org","threadId":"29892","inReplyTo":null,"subject":"how to patch git documentation","fromName":"Neal Kreitzinger","fromEmail":"nkreitzinger@gmail.com","sentAt":"2012-03-09T02:38:01Z","receivedAt":"2012-03-09T02:38:01Z","isPatch":false,"sender":{"key":"nkreitzinger@gmail.com","avatar":null},"body":"Is there a document on how to patch git documentation?\n\nBasic question:\nWhat language are the git documentation *.txt files written in?\n\nv/r,\nneal\n"},{"id":"186518","messageId":"7v1up2bikm.fsf@alter.siamese.dyndns.org","threadId":"29892","inReplyTo":"jjbqe9$8l3$1@dough.gmane.org","subject":"Re: how to patch git documentation","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-09T02:43:05Z","receivedAt":"2012-03-09T02:43:05Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Neal Kreitzinger <nkreitzinger@gmail.com> writes:\n\n> What language are the git documentation *.txt files written in?\n\nMixture of Pidgin English and a bit of AsciiDoc ;-).\n"},{"id":"186522","messageId":"4F5991D8.60207@gmail.com","threadId":"29892","inReplyTo":"7v1up2bikm.fsf@alter.siamese.dyndns.org","subject":"Re: how to patch git documentation","fromName":"Neal Kreitzinger","fromEmail":"nkreitzinger@gmail.com","sentAt":"2012-03-09T05:15:04Z","receivedAt":"2012-03-09T05:15:04Z","isPatch":false,"sender":{"key":"nkreitzinger@gmail.com","avatar":null},"body":"On 3/8/2012 8:43 PM, Junio C Hamano wrote:\n> Neal Kreitzinger<nkreitzinger@gmail.com>  writes:\n>\n>> What language are the git documentation *.txt files written in?\n>\n> Mixture of Pidgin English and a bit of AsciiDoc ;-).\n>\nIs it ok to submit patches to git.git using msysgit, and also from \ngit-osx?  I'm not sure how fast I can get past our security people on \nthe linux servers, if at all.\n\nv/r,\nneal\n"},{"id":"186525","messageId":"7vk42u9ve2.fsf@alter.siamese.dyndns.org","threadId":"29892","inReplyTo":"4F5991D8.60207@gmail.com","subject":"Re: how to patch git documentation","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-09T05:49:09Z","receivedAt":"2012-03-09T05:49:09Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Neal Kreitzinger <nkreitzinger@gmail.com> writes:\n\n> On 3/8/2012 8:43 PM, Junio C Hamano wrote:\n>> Neal Kreitzinger<nkreitzinger@gmail.com>  writes:\n>>\n>>> What language are the git documentation *.txt files written in?\n>>\n>> Mixture of Pidgin English and a bit of AsciiDoc ;-).\n>>\n> Is it ok to submit patches to git.git using msysgit, and also from\n> git-osx?  I'm not sure how fast I can get past our security people on\n> the linux servers, if at all.\n\nHonestly, I highly doubt if I could even tell if your patch was\ncreated with \"git format-patch\" running on Linux, Mac OS X, Windows,\nor CP/M-86 for that matter.  As long as the port of Git to the\nplatform is working correctly, that is.\n"},{"id":"186601","messageId":"4F5A8E0C.20404@gmail.com","threadId":"29892","inReplyTo":"7v1up2bikm.fsf@alter.siamese.dyndns.org","subject":"Re: how to patch git documentation","fromName":"Neal Kreitzinger","fromEmail":"nkreitzinger@gmail.com","sentAt":"2012-03-09T23:11:08Z","receivedAt":"2012-03-09T23:11:08Z","isPatch":false,"sender":{"key":"nkreitzinger@gmail.com","avatar":null},"body":"On 3/8/2012 8:43 PM, Junio C Hamano wrote:\n> Neal Kreitzinger<nkreitzinger@gmail.com>  writes:\n>\n>> What language are the git documentation *.txt files written in?\n> Mixture of Pidgin English and a bit of AsciiDoc ;-).\n>\n>\nDoes someone have documentation on how to test the AsciiDoc changes of \ntheir Documentation/ patches?  This tester I found doesn't work right \nbecause it not only shows my asciidoc changes misformatted in html, but \nit also shows the original working asciidoc code from git.git as being \nmisformatted in html :  http://andrewk.webfactional.com/asciidoc.php\n\nv/r,\nneal\n"}]}