From owner-freebsd-bugs Wed Jan 9 6:50:41 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CD5C037B41E; Wed, 9 Jan 2002 06:50:38 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g09EmNc87331; Wed, 9 Jan 2002 06:48:23 -0800 (PST) (envelope-from sheldonh) Date: Wed, 9 Jan 2002 06:48:23 -0800 (PST) From: Message-Id: <200201091448.g09EmNc87331@freefall.freebsd.org> To: mike_makonnen@yahoo.com, sheldonh@FreeBSD.org, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/33187: [PATCH] /bin/ls -dF adds trailing slash regardless of whether there is already one there Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [PATCH] /bin/ls -dF adds trailing slash regardless of whether there is already one there State-Changed-From-To: open->suspended State-Changed-By: sheldonh State-Changed-When: Wed Jan 9 06:46:28 PST 2002 State-Changed-Why: There doesn't seem to be an easy way to handle this. For now, it's probably better to simply fix scripts that use ls -dF output. For the record, I'm pretty sure I remember POSIX warning against relying on the output of ls(1) in scripts. Responsible-Changed-From-To: sheldonh->freebsd-bugs Responsible-Changed-By: sheldonh Responsible-Changed-When: Wed Jan 9 06:46:28 PST 2002 Responsible-Changed-Why: Leave this one for another brave soul. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33187 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message