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

Re: [PATCH] \n usage in stderr output

From
Petr Baudis <pasky@suse.cz>
Date
Dec 15, 2005, 08:52 UTC
Message-ID
<20051215085242.GO22159@pasky.or.cz>
In-Reply-To
<81b0412b0512142347o6e9aaef8s227ad749f3e2a475@mail.gmail.com>

Dear diary, on Thu, Dec 15, 2005 at 08:47:30AM CET, I got a letter where Alex Riesen <raa.lkml@gmail.com> said that...

> fprintf and die sometimes have missing/excessive "\n" in their arguments,
> correct the strings where I think it would be appropriate.
> 
> Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
Why don't we just error() or die() at those places anyway?
-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
Previous: Alex RiesenNext: Alex Riesen
Message 2 of 3 in “\n usage in stderr output”
  1. \n usage in stderr outputAlex Riesen, Dec 15, 2005
  2. Petr BaudisDec 15, 2005
  3. Alex RiesenDec 15, 2005

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.