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

Re: [PATCH] Documentation/CodingGuidelines: improve header includes rules

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 14, 2009, 16:24 UTC
Message-ID
<alpine.DEB.1.00.0904141822030.10279@pacific.mpi-cbg.de>
In-Reply-To
<20090414003433.39cbdea2.chriscool@tuxfamily.org>
Hi,
On Tue, 14 Apr 2009, Christian Couder wrote:
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
>  Documentation/CodingGuidelines |   26 ++++++++++++++++++++++----
>  1 files changed, 22 insertions(+), 4 deletions(-)

I think that there is a very real possiblity here to make this document so long that hardly anybody reads it to the end.

And is there not a real chance that your change is actually covered by
	As for more concrete guidelines, just imitate the existing code
?

Ciao, Dscho

Previous: Christian CouderNext: Jeff King
Message 2 of 4 in “Documentation/CodingGuidelines: improve header includes rules”
  1. Documentation/CodingGuidelines: improve header includes rulesChristian Couder, Apr 13, 2009
  2. Johannes SchindelinApr 14, 2009
  3. Jeff KingApr 15, 2009
  4. Christian CouderApr 16, 2009

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.