News for hackers. Stuff that matters.
Re:An Ancient Kernel Hole Is Not Closed by daveguy on Wednesday June 21, 2017 @12:01AM (#14600555)
So the title should read "is not closed"? The parenthesis are just annoying. It's one or the other, just state it!

Readers shouldn't have to solve a puzzle to read a title.

Re:An Ancient Kernel Hole Is Not Closed by nullc on Wednesday June 21, 2017 @02:03AM (#14601121)
The title is a play on a 2010 LWN headline.

This is explained in the article.

But reading the article has never been a barrier for HN editing a headline to make it less accurate in the past, so why start now? :)

Re:An Ancient Kernel Hole Is Not Closed by sdrothrock on Wednesday June 21, 2017 @12:14AM (#14600606)
First read to me as someone who hadn't read the article was "someone found an ancient kernel hole and declared it closed, but in truth it's actually not," which actually seems to be what was intended... it's a fairly common use of "(not)."
Re:An Ancient Kernel Hole Is Not Closed by CaliforniaKarl on Wednesday June 21, 2017 @02:59AM (#14601480)
I'm sorry, I'm really confused now.

Here's the title of the article:

An Ancient Kernel Hole is (Not) Closed

I thought that I copy-pasted the article title to be the title of this submission.

Did I omit the parenthesis? If so, it was unintentional, and I apologize.

Re:An Ancient Kernel Hole Is Not Closed by enzanki_ars on Wednesday June 21, 2017 @06:39AM (#14602551)
HN automatically removes certain punctuation from post titles. In a lot of cases though, it creates more confusion. Definitely not your fault.
Re:An Ancient Kernel Hole Is Not Closed by CaliforniaKarl on Wednesday June 21, 2017 @10:51AM (#14604259)
I did not know that! I'm tempted to experiment now 8-)

Thanks for the heads-up!