X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL,BAYES_00,TW_CG,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4C094B0D.5010406@cs.umass.edu>
Date: Fri, 04 Jun 2010 14:50:53 -0400
From: Eliot Moss <moss@cs.umass.edu>
Reply-To: moss@cs.umass.edu
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Cygwin Performance and stat()
References: <4C03D6C5.4050004@x-ray.at>    <80373222dd5d43b134a5ede7036e7674.squirrel@www.webmail.wingert.org>    <20100602080626.GV16885@calimero.vinschen.de>    <383c8b44a088dad09a0b77d3299feda7.squirrel@www.webmail.wingert.org>    <20100602174848.GA14172@ednor.casa.cgf.cx>    <e13dc87c8ea561acfd167ec92bb737cf.squirrel@www.webmail.wingert.org>    <20100603235944.GA12167@ednor.casa.cgf.cx>    <c2b0024257b44cff37a8f24b4c592f1b.squirrel@www.webmail.wingert.org>    <20100604024422.GB12167@ednor.casa.cgf.cx>    <78e7b77657c0cfcd63dc22ad9679bc85.squirrel@www.webmail.wingert.org>    <20100604045807.GC12167@ednor.casa.cgf.cx>    <2570318aabfa537bf24c8d3a55f9dcd4.squirrel@www.webmail.wingert.org>    <4C092F96.5040800@cygwin.com> <7a1785a5f0a1d0a8956cd10e573f2e53.squirrel@www.webmail.wingert.org>
In-Reply-To: <7a1785a5f0a1d0a8956cd10e573f2e53.squirrel@www.webmail.wingert.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

I don't think there's an objection here to
patching *rsync* specially in the cygwin
environment -- that would be between you
and the rsync port maintainer. The issue
is whether or not to make a more general
change to cygwin itself, and cgf is just
saying that that's hard to do.

Conceivably we could come up with some
additional functions that cygwin ports
could use if they want to, but "out of
box" use of stat needs to replicate
full behavior since there's no way to
know what a given call of stat really
needs ...

Eliot Moss

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

