X-Recipient:	archive-cygwin AT delorie DOT 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=Xu8XgCwctDRBxbS/WTptdRdboMeyMRPaJHyNzufUwZXHDoyPVaZQf
	KmeUsi+Qm59eTdqTsqyPvb3Y1SO9RB/x6PGh5YY4kR5varaCPxT/Oa3qV2YLP01Z
	GjdqtLmfg4mwQkM5ldw3UPdgJCf93rjfVRm8ID1PsAhHWp0sY7iBKw=
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=UzcE4uWoetmNZ1ZFc8khWGS9W/Y=; b=hTtuKAk1e+NWeY0Hj7FLsn9HQfmW
	gQsfh+CgmQZNZJEHm3k/zJlE4/7Pl+Yqw9WZj0ol1ZeGp0o5BE9SjTPhnNFBiusV
	chSUpMPtCuC/noB1Mj4cR9eqgnxBYi4evADYwGtZ7tg1QPC3w49rjdtaqgAi61ru
	d5o3oOWFHqstRNA=
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
X-Spam-SWARE-Status:	No, score=1.2 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RDNS_NONE autolearn=no version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1/OvTjlyb0xUs8TdwZW8Ukn
Date:	Thu, 25 Jul 2013 23:10:48 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: python aborts
Message-ID:	<20130726031048.GD1954@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<51F0CBD2 DOT 2030502 AT dancol DOT org> <51F0CF92 DOT 60009 AT dancol DOT org> <51F0E39C DOT 1090500 AT dancol DOT org> <20130725091741 DOT GA20682 AT calimero DOT vinschen DOT de> <51F0FB68 DOT 90904 AT gmail DOT com> <51F103CB DOT 20904 AT gmail DOT com> <20130725151410 DOT GB6932 AT ednor DOT casa DOT cgf DOT cx> <51F14DE9 DOT 7050702 AT gmail DOT com> <20130725172007 DOT GC6019 AT ednor DOT casa DOT cgf DOT cx> <51F1A3AA DOT 5040804 AT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<51F1A3AA.5040804@gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

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.

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

- Raw text -