From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Tue, 21 Dec 2004 15:18:50 +0000 Subject: Re: parser problem Message-Id: <20041221151850.GB12746@kroah.com> List-Id: References: <20041221141751.GA11862@cirrus.madduck.net> In-Reply-To: <20041221141751.GA11862@cirrus.madduck.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Tue, Dec 21, 2004 at 03:50:38PM +0100, martin f krafft wrote: > also sprach martin f krafft [2004.12.21.1517 +0100]: > > chmod'd to 660. Seems like the newline causes udev to ignore the > > previous match specification. > > So noticing the recent announcement where multiline is a feature > request, I tried to figure out why I thought that it can be > multiline in the first place. My first guess was because of the > commas, which seem to be syntactic sugar without a real purpose. The commas define the different fields in a line. All udev rules are single line, that is why people have recently asked for longer ones. > More readable to me is <80 columns. > > Oh well, apparently we now have to define permissions policy in > column 190. Yeah udev! Um, Kay just provided a patch to allow longer lines. What's the problem with that? And hey, what's wrong with 190 column lines, just use a tiny font :) greg k-h ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel