X-Recipient: archive-cygwin@delorie.com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=rKNUDCi048dCCDZPkwcvB7Ypaftfz22eCGXpNU8H5nRWaIdBFKHut bvQJTId2uGft6HwfrSeKs39gKyW+vFJ11zUAJrIq/LaS3bbmX6s4ri6ShFaz/z/z vH+v3X/318jHYEeSB9WeONcoA6se9sm4Ybr5gn4YMh5MZnLgfqCAY8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=tvdXq+VMfQhw+niBt2YzmECnoYI=; b=g1mBav9J7KEZR/kXPn6LoBvZTAmf DeH/Fmnshdo2S3noe32Qnk6t5Y9CfMN1ao7jFGQweQ6P8owQarYcdYvLOHJwZwwb xCmuN2MkdVIAvVvGSTUNKHfxz8nqRhae3DRMCVTRTp+F24dP8iYSvyC0P+xBb4hg NpwOEhpuawYmY/Q= Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.2 required=5.0 tests=AWL,BAYES_00,FSL_HELO_NON_FQDN_1,HELO_LOCALHOST,RCVD_IN_PBL,RCVD_IN_RP_RNBL,RCVD_IN_SORBS_DUL,RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: mho-02-ewr.mailhop.org X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/hArucHDqxFyKCyml5iblM Date: Tue, 27 Aug 2013 23:59:43 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: python aborts Message-ID: <20130828035943.GA6973@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <51F0CF92.60009@dancol.org> <51F0E39C.1090500@dancol.org> <20130725091741.GA20682@calimero.vinschen.de> <51F0FB68.90904@gmail.com> <51F103CB.20904@gmail.com> <20130725151410.GB6932@ednor.casa.cgf.cx> <51F14DE9.7050702@gmail.com> <20130725172007.GC6019@ednor.casa.cgf.cx> <51F1A3AA.5040804@gmail.com> <20130726031048.GD1954@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130726031048.GD1954@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) On Thu, Jul 25, 2013 at 11:10:48PM -0400, Christopher Faylor wrote: >On Fri, Jul 26, 2013 at 06:16:10AM +0800, JonY wrote: >>On 7/26/2013 01:20, Christopher Faylor wrote: >>> On Fri, Jul 26, 2013 at 12:10:17AM +0800, JonY wrote: >>>> On 7/25/2013 23:14, Christopher Faylor wrote: >>>>> >>>>> I'm still a (silent) gcc maintainer so I can presumably accept this patch. >>>>> >>>>> Are there outstanding patches that need attention? If so, please send URLs >>>>> from the gcc-patches archive here so that I can attend to them. >>>>> >>>> >>>> This libgcc patch, and some minor patches at >>>> http://gcc.gnu.org/ml/gcc-patches/2013-07/msg00416.html. >>>> >>>> There are some others from Yaakov's gcc builds, but let's start with >>>> smaller patches first. >>> >>> It will probably be a couple of days before I can give these adequate >>> attention. >>> >>> Ok to submit your name as an upstream approver, JonY? >>> >> >>I have not approved any patches for GCC, not sure if I can act as >>approver. Kai usually approves and commits any mingw* related gcc >>patches but he is not in currently. > >Uh, yeah. AFAIK, you aren't listed as a package approver so it would be >very difficult for you to approve anything. > >Ok, nevermind. Did this ever get resolved? Did Kai apply the patches? 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