X-Recipient: archive-cygwin AT delorie DOT 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 Reply-To: moss AT cs DOT umass DOT 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 AT cygwin DOT com Subject: Re: Cygwin Performance and stat() References: <4C03D6C5 DOT 4050004 AT x-ray DOT at> <80373222dd5d43b134a5ede7036e7674 DOT squirrel AT www DOT webmail DOT wingert DOT org> <20100602080626 DOT GV16885 AT calimero DOT vinschen DOT de> <383c8b44a088dad09a0b77d3299feda7 DOT squirrel AT www DOT webmail DOT wingert DOT org> <20100602174848 DOT GA14172 AT ednor DOT casa DOT cgf DOT cx> <20100603235944 DOT GA12167 AT ednor DOT casa DOT cgf DOT cx> <20100604024422 DOT GB12167 AT ednor DOT casa DOT cgf DOT cx> <78e7b77657c0cfcd63dc22ad9679bc85 DOT squirrel AT www DOT webmail DOT wingert DOT org> <20100604045807 DOT GC12167 AT ednor DOT casa DOT cgf DOT cx> <2570318aabfa537bf24c8d3a55f9dcd4 DOT squirrel AT www DOT webmail DOT wingert DOT org> <4C092F96 DOT 5040800 AT cygwin DOT com> <7a1785a5f0a1d0a8956cd10e573f2e53 DOT squirrel AT www DOT webmail DOT wingert DOT 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 AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT 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