git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: how to patch git documentation

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 9, 2012, 05:49 UTC
Message-ID
<7vk42u9ve2.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4F5991D8.60207@gmail.com>
Neal Kreitzinger <nkreitzinger@gmail.com> writes:
Show 10 quoted lines
> 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.

Previous: Neal KreitzingerNext: Neal Kreitzinger
Message 4 of 5 in “how to patch git documentation”
  1. Neal KreitzingerMar 9, 2012
  2. Junio C HamanoMar 9, 2012
  3. Neal KreitzingerMar 9, 2012
  4. Junio C HamanoMar 9, 2012
  5. Neal KreitzingerMar 9, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.