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

Re: Aw: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 30, 2012, 21:40 UTC
Message-ID
<7v1ue7fcbh.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1965427282.405137.1356879393533.JavaMail.ngmail@webmail18.arcor-online.net>
Thomas Ackermann <th.acker@arcor.de> writes:
>  
> ./Documentation/technical contains not only API documentation but also
> several other documents describing Git implementation topics and thus
> is the place someone wanting to join Git development should look at.

Implementation details are part of API; CG and SP are social not technical.

Also CG and SP are in the part of the documents that are not installed for end-users and that is their right place. They matter only to the people who grab our source code.

Previous: Thomas AckermannNext: Thomas Ackermann
Message 2 of 3 in “Aw: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technical”
  1. Thomas AckermannDec 30, 2012
  2. Junio C HamanoDec 30, 2012
  3. Aw: Re: Aw: Re: [PATCH 0/3] Move CodingGuidelines and SubmittingPatches to ./Documentation/technicalThomas Ackermann, Dec 31, 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.