From owner-freebsd-bugs Thu Aug 12 19: 1:14 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E0EE114CD1 for ; Thu, 12 Aug 1999 19:01:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id TAA39654; Thu, 12 Aug 1999 19:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 12 Aug 1999 19:00:02 -0700 (PDT) Message-Id: <199908130200.TAA39654@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Danny J. Zerkel" Subject: Re: bin/4420: find -exedir doesn't chdir for first entry Reply-To: "Danny J. Zerkel" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/4420; it has been noted by GNATS. From: "Danny J. Zerkel" To: freebsd-gnats-submit@freebsd.org, imp@village.org Cc: Subject: Re: bin/4420: find -exedir doesn't chdir for first entry Date: Thu, 12 Aug 1999 21:54:00 -0400 > From: Bruce Evans > > The XXX comment in f_exedir() says that paths with trailing slashes are > mishandled if they actually occur. Ahh, yes. Didn't think about it from that end of the path. Well, my patch does nothing to repair or further break that mishandling. I suppose one could set {} to '.'. It would be technically correct, but the ramifications would be difficult to guess. -- Danny J. Zerkel dzerkel@columbus.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message