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

[PATCH] Coding guideline for Error messages

From
Philip Oakley <philipoakley@iee.org>
Date
Jun 16, 2014, 12:55 UTC
Message-ID
<1402923357-3788-1-git-send-email-philipoakley@iee.org>

A recent review comment highlighted the current view on error message punctuation. I thought it worth recording.

In the past I've also seen guidance on the error message style. This patch also gives a place for recording such guidance, for example, ensuring that the message is useful to the user, rather than referring to some internal technical issue. I haven't looked deeply for those yet.

Philip Oakley (1):
  doc: State coding guideline for error message punctuation
 Documentation/CodingGuidelines | 7 +++++++
 1 file changed, 7 insertions(+)
-- 
1.9.4.msysgit.0
Next: Philip Oakley
Message 1 of 8 in “Coding guideline for Error messages”
  1. Coding guideline for Error messagesPhilip Oakley, Jun 16, 2014
  2. doc: State coding guideline for error message punctuationPhilip Oakley, Jun 16, 2014
  3. Junio C HamanoJun 16, 2014
  4. Philip OakleyJun 16, 2014
  5. Jeff KingJun 17, 2014
  6. Junio C HamanoJul 10, 2014
  7. Jeff KingJul 10, 2014
  8. Philip OakleyJul 15, 2014

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.