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

Re: [PATCH] doc: State coding guideline for error message punctuation

From
Jeff King <peff@peff.net>
Date
Jul 10, 2014, 20:42 UTC
Message-ID
<20140710204228.GA4459@sigill.intra.peff.net>
In-Reply-To
<xmqqwqbl6jey.fsf@gitster.dls.corp.google.com>
On Thu, Jul 10, 2014 at 01:36:05PM -0700, Junio C Hamano wrote:
Show 6 quoted lines
> > Perhaps there are others (we do not have to be exhaustive, but it makes
> > sense to think for a moment while we are here).
> 
> I do not want to forever be waiting for a reroll, so let's queue
> this and advance it to 'next' soonish, and refine the guidelines by
> further building on top of it as needed.
Yes, that looks good to me. Thanks for moving this forward.
-Peff
Previous: Junio C HamanoNext: Philip Oakley
Message 7 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.