Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com From: =?ISO-8859-1?Q?Sven_K=F6hler?= Subject: Re: odd behavior of symlinks on Win XP SP2 Date: Mon, 17 Jan 2005 22:33:47 +0100 Lines: 11 Message-ID: References: <200501171625.j0HGPQM13040@networking.Stanford.EDU> <20050117171226.GJ20403@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: dsl-082-083-011-111.arcor-ip.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20050111 In-Reply-To: <20050117171226.GJ20403@trixie.casa.cgf.cx> X-IsSubscribed: yes >>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. This comment is ridiculous. He clearly complained about MS-Software that cannot handle cygwin-created links, and you're talking about cygwin understand its own symlinks - well, think about it again. -- 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/