Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<5.0.2.1.0.20010223120510.02408cf0@mailhost>
X-Sender:	paulson AT mailhost
X-Mailer:	QUALCOMM Windows Eudora Version 5.0.2
Date:	Fri, 23 Feb 2001 12:11:36 -0800
To:	cygwin AT sources DOT redhat DOT com
From:	John Paulson <munch AT powertv DOT com>
Subject:	Re: [ANNOUNCEMENT]: Important change to symbolic link
	functionality
Mime-Version:	1.0

   I like the proposal to unify Windows and Cygwin symlinks.  However, one
minor problem can occur: under *nix I can have files with the extension
.lnk, with no special semantics associated with it.  I can tar up a directory
containing .lnk files on my *nix box and untar them on my cygwin box.  What
happens to those files with the .lnk extension?  I think this will be another
bit of Windows-vs-the-world festivity (as occurred with one source tarball
recently which had a directory named "AUX").

   Even with that potential hassle, unification is the correct choice.


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -