[PATCH] \n usage in stderr output

STALE3715d

3 messages, 2 authors, 2016-06-15 · open the first message on its own page

[PATCH] \n usage in stderr output

From: Alex Riesen <hidden>
Date: 2016-06-15 22:42:14

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 <redacted>

---

It is always stderr, so I can hope I am not breaking anyones script...

Re: [PATCH] \n usage in stderr output

From: Petr Baudis <hidden>
Date: 2016-06-15 22:42:14

Dear diary, on Thu, Dec 15, 2005 at 08:47:30AM CET, I got a letter
where Alex Riesen [off-list ref] 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 <redacted>
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.

Re: [PATCH] \n usage in stderr output

From: Alex Riesen <hidden>
Date: 2016-06-15 22:42:15

On 12/15/05, Petr Baudis [off-list ref] wrote:
quoted
fprintf and die sometimes have missing/excessive "\n" in their arguments,
correct the strings where I think it would be appropriate.
Why don't we just error() or die() at those places anyway?
I don't know.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help