X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Eric Blake <ebb9 AT byu DOT net>
Subject:  Re: [ANNOUNCEMENT] Updated: coreutils-6.10-1
Date: Mon, 14 Apr 2008 21:10:52 +0000 (UTC)
Lines: 19
Message-ID:  <loom.20080414T210749-703@post.gmane.org>
References:  <announce DOT 47A62BF1 DOT 8050004 AT byu DOT net> <20080411171048 DOT GV23852 AT calimero DOT vinschen DOT de>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:

> 
> These are the changes noted in the changelog.  However, what I see now
> is that the target of a symlink is not colored anymore at all.

According to the upstream maintainer, this was a deliberate change (even though 
it was not mentioned in NEWS).  
http://thread.gmane.org/gmane.os.cygwin/95238/focus=13223
The cost of stat'ing a known symlink (which may involve spinning up a disk or 
doing a network access) just to color its target was deemed too expensive for 
the default.  Coreutils 6.11 is due out this week, with no change in behavior, 
but perhaps for 6.12, upstream can add a option to dircolors/ls that requests 
coloring symlink targets in spite of the increased cost of the stat.

-- 
Eric Blake




--
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/