[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFz4E_zkoZvM9mO0v4cZU7Y-VZhGYRC0OzLPvB5tgqwi=w@mail.gmail.com>
Date: Tue, 29 Aug 2017 10:36:09 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Joe Perches <joe@...ches.com>
Cc: Pavel Machek <pavel@....cz>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>, Jan Kara <jack@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Jiri Slaby <jslaby@...e.com>, Andreas Mohr <andi@...as.de>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: printk: what is going on with additional newlines?
On Tue, Aug 29, 2017 at 10:33 AM, Joe Perches <joe@...ches.com> wrote:
>
> Your change broke a bunch of output.
Tough. We've done that before to force people to fix their code.
I'm actually upset that EVEN NOW (and it's been, what, 18 months),
people ask for the old broken shit behavior back.
It's ten years since we introduced the marker, and it's been over a
year since I made that pretty much a requirement, and people still
want to do the broken crap.
I'm not AT ALL feeling sorry for people. Fix your shit, or see ugly
output. Those are the two choices.
Linus
Powered by blists - more mailing lists