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 Date: Mon, 17 Jan 2005 17:07:56 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: odd behavior of symlinks on Win XP SP2 Message-ID: <20050117220756.GJ22849@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <200501171625.j0HGPQM13040@networking.Stanford.EDU> <20050117171226.GJ20403@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Mon, Jan 17, 2005 at 10:33:47PM +0100, Sven K?hler wrote: >>>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. Apologies. I took the word "altogether" to mean "completely" but obviously missed the meaning implied by "from the windoze perspective". 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/