Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 17 Jan 2005 12:12:26 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: odd behavior of symlinks on Win XP SP2
Message-ID: <20050117171226.GJ20403@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <corinna-cygwin AT cygwin DOT com> <200501171625 DOT j0HGPQM13040 AT networking DOT Stanford DOT EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200501171625.j0HGPQM13040@networking.Stanford.EDU>
User-Agent: Mutt/1.4.1i

On Mon, Jan 17, 2005 at 08:25:26AM -0800, Jeff DOT Hodges AT KingsMountain DOT com wrote:
>> I'm glad that you're talking about "us" as a group.  Anybody interested
>> in tracking that down?
>
>I'm not in a position to hack code on this unfortunately, but I can offer to 
>test.
>
>I suspect it's important in the longer term to track this down because they 
>(MSFT) ~could~ make further changes down the road that break cygwin-created 
>symlinks altogether (from the windoze perspective), which'd more than just 
>"annoying".

No, Microsoft is not going to break things so that cygwin's symlinks no
longer operate.  Cygwin understands its own version of symlinks very well.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/