From owner-cvs-all  Thu Mar 15 11:41: 8 2001
Delivered-To: cvs-all@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP
	id 80A3137B71A; Thu, 15 Mar 2001 11:41:03 -0800 (PST)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA48323;
	Thu, 15 Mar 2001 14:40:58 -0500 (EST)
	(envelope-from wollman)
Date: Thu, 15 Mar 2001 14:40:58 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200103151940.OAA48323@khavrinen.lcs.mit.edu>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/lib/libc/gen glob.c 
In-Reply-To: <8030.984684752@critter>
References: <20010315132503.D82645@prism.flugsvamp.com>
	<8030.984684752@critter>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<<On Thu, 15 Mar 2001 20:32:32 +0100, Poul-Henning Kamp <phk@critter.freebsd.dk> said:

> 	"../barf/.." = BAD

This does not seem correct.  I think I have an idea of what you're
trying to prevent, but in the case where `../barf' is a symbolic link,
`../barf/..' is a useful way to get to the parent of wherever
`../barf' points.

Can you think of an example where this is a problem, that doesn't
involve globbing?

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message