Date: Mon, 02 Jul 2001 17:06:45 -0700 From: Dima Dorfman <dima@unixfreak.org> To: Alfred Perlstein <bright@sneakerz.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sbin/mountd mountd.c Message-ID: <20010703000646.13F1A3E28@bazooka.unixfreak.org> In-Reply-To: <20010702185739.X84523@sneakerz.org>; from bright@sneakerz.org on "Mon, 2 Jul 2001 18:57:39 -0500"
next in thread | previous in thread | raw e-mail | index | archive | help
Alfred Perlstein <bright@sneakerz.org> writes: > * Dima Dorfman <dd@FreeBSD.org> [010702 18:56] wrote: > > dd 2001/07/02 16:56:01 PDT > > > > Modified files: > > sbin/mountd mountd.c > > Log: > > Correct handling of continuation lines. Instead of treating the > > backslash as nothing, treat it like a space so that adjacent lines > > aren't glued together. > > So now how does one use a backslash when one doesn't want a space? Where would you want to use a backslash? AFAIK there are no parameters in exports(5) where a backslash would be valid. If you're talking about using it in the middle of a word and at the end of the line, like this: /usr -alldirs -netw\ ork=fish host1 host2 then this commit puts you out of luck. However, I honestly don't see why somebody would want to do that. The new sematic is much more intuitive and in line with most (every?) other file format that supports continuation lines. I think it's what most people would expect when they use a backslash at the end of a line. Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010703000646.13F1A3E28>