X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Resent-From: Christopher Faylor Resent-Date: Fri, 4 Jun 2010 13:52:25 -0400 Resent-Message-ID: <20100604175225 DOT GA16786 AT ednor DOT casa DOT cgf DOT cx> Resent-To: cygwin AT cygwin DOT com Date: Fri, 4 Jun 2010 13:29:46 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cygwin Performance and stat() Message-ID: <20100604172946.GA12570@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7a1785a5f0a1d0a8956cd10e573f2e53.squirrel@www.webmail.wingert.org> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Fri, Jun 04, 2010 at 10:07:58AM -0700, Christopher Wingert wrote: >Again, not production, this was to highlight a point and to enhance (I >would assume) the most common use case (file to file rsync). > >Plenty of solutions for a good patch, complete the Windows version of >stat() or call the Cygwin version if the Window's version fails. > >Since I don't have any confidence that the "Cygwin organization" will >accept any patch I write (per Faylor), I really have no incentive to do >the job right. Actually, I pointed you at the web site so that you could find out what needs to be done for a patch to be accepted. From http://cygwin.com/ml/cygwin/2010-06/msg00103.html: "Btw, if you are considering a patch, you should check out the link on the website for what you need to do there. In a nutshell: we have a procedure similar to the FSF except that changes need to be assigned to Red Hat." I thought I could use a little short-hand there since you professed to be familiar with other open source projects but maybe I shouldn't have assumed. For a non-trivial patch to be accepted into the code base you need to assign the rights to Red Hat. I mentioned this now so that the paperwork could potentially be in process while the patch was being worked on. The Contributing link on the web site has more details. Also, if you want to avoid further confusion about who is doing what on the project you can check out the Community link. cgf -- 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