From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 208E865DEB for ; Thu, 30 Oct 2014 17:28:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id s9UHRAea025452; Thu, 30 Oct 2014 17:27:33 GMT Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id v_bTAb4896eG; Thu, 30 Oct 2014 17:27:33 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id s9UHRVeT025469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 30 Oct 2014 17:27:32 GMT Message-ID: <1414690086.7649.63.camel@ted> From: Richard Purdie To: Andreas =?ISO-8859-1?Q?M=FCller?= Date: Thu, 30 Oct 2014 17:28:06 +0000 In-Reply-To: References: <1414508747-4688-1-git-send-email-gary@mlbassoc.com> <54525BA9.9000606@mlbassoc.com> X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Cc: Gary Thomas , OE-core Subject: Re: [PATCH] python-pygtk: Restore pkg-config file X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 17:28:11 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit On Thu, 2014-10-30 at 17:14 +0100, Andreas Müller wrote: > On Thu, Oct 30, 2014 at 4:39 PM, Gary Thomas wrote: > > > > Wow, since Jan 2013 and no action? > > > > Was this proposed to OE-core (i.e. sent to the list)? > > > No - my expiereineces sending patches to oe-core are not the best. > Usually they just cause me efforts and aren't applied anyway.. Its sad that you feel that and if we can, I'd like to try and fix that somehow. People do try their best, equally, the response against the maintainers if something goes wrong hasn't been ideal either. Is there anything specific we can try and do better? Cheers, Richard