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

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

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Dec 30, 2012, 11:52 UTC
Message-ID
<CALkWK0=FFt2qfrUop9kwDVQ1FfPm+4WY8kBBY+rtyp16QFOR_A@mail.gmail.com>
In-Reply-To
<1023165134.213650.1356863340563.JavaMail.ngmail@webmail06.arcor-online.net>
Thomas Ackermann wrote:
> CodingGuidelines and SubmittingPatches are IMHO a little bit hidden in ./Documentation
> and with respect to their content should be better placed in ./Documentation/technical.

I don't think SubmittingPatches and CodingGuidelines belong to Documentation/technical; that location is mostly reserved for API documentation. Also, being prominent documents, they're probably linked to by many places on the internet. I wouldn't want to unnecessarily break those links.

Ram
Previous: Thomas Ackermann
Message 5 of 5 in “Move CodingGuidelines and SubmittingPatches to ./Documentation/technical”
  1. 0/3 Move CodingGuidelines and SubmittingPatches to ./Documentation/technicalThomas Ackermann, Dec 30, 2012
  2. 1/3 Move CodingGuidelines to ./technical/coding-guidelines.txt and SubmittingPatches to ./technical/submitting-patches.txtThomas Ackermann, Dec 30, 2012
  3. 2/3 Add coding-guidelines.txt and submitting-patches.txt to ./Documentation/MakefileThomas Ackermann, Dec 30, 2012
  4. 3/3 Convert coding-guidelines.txt and submitting-patches.txt to asciidocThomas Ackermann, Dec 30, 2012
  5. Ramkumar RamachandraDec 30, 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.