JG> Now what did that blank line do to you to deserve that? Who knows
JG> how many compile cycles it's mutely stood witness as all the other
JG> lines get to become things like control structures and
JG> keywords. And what is its reward for a near eternity of silent
JG> service? A summary deletion, with a mere one-character obituary
JG> buried in a diff on a mailing list, read by few and noticed by
JG> fewer. Well, I noticed, and I won't stand for it!
/me stares at the screen in amazement
JG> On top of killing the "." and ".." listings, this will also
skip
JG> all hidden (.foo) files. This is of course fine by me, but just
JG> checking that this is the intended behavior.
Yes, I think that's a good thing. If someone goes to look in, or
clear out that directory to be "safe", hidden files could cause
confusion and risk. It's also a reasonable way for people to disable
a check temporarily, by making it hidden.
A new set without the senseless killing of a blank line is on the
way.
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com