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

Re: [PATCH 4/4] gitweb: No periods for error messages

From
LTLuben Tuikov <ltuikov@yahoo.com>
Date
Aug 5, 2006, 01:03 UTC
Message-ID
<20060805010307.17651.qmail@web31807.mail.mud.yahoo.com>
In-Reply-To
<7vpsfgghi2.fsf@assigned-by-dhcp.cox.net>
--- Junio C Hamano <junkio@cox.net> wrote:
> This and Jakub's [1/5] seem to be going the opposite way.
Not quite.  They both do the same thing, except his patch
does it only half way: 
  - no full stop for error messages ending with some kind
    of variable expansion.
  - full stop for static error messages.
> I tend to prefer ending each sentence with a full stop.
I've never seen this in, among other things,
  - kernel messages
  - errno messages
  - web server messages
  - RFC text describing error messages, (web services),
  - etc.
I was going for was consistency.  I'd say apply Jacob's [6/5].
   Luben
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 4 in “gitweb: No periods for error messages”
  1. 4/4 gitweb: No periods for error messagesLuben Tuikov, Aug 4, 2006
  2. Junio C HamanoAug 5, 2006
  3. Luben TuikovAug 5, 2006
  4. Junio C HamanoAug 5, 2006

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.