From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [81.169.183.159] (helo=coruscant.onosendai.de) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1KqFAE-0007So-Ql for openembedded-devel@lists.openembedded.org; Thu, 16 Oct 2008 00:48:22 +0200 Received: from [92.116.127.219] (helo=[10.129.127.219]) by coruscant.onosendai.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1KqF5D-0007bo-VW for openembedded-devel@lists.openembedded.org; Thu, 16 Oct 2008 00:43:12 +0200 From: Holger Freyther To: openembedded-devel@lists.openembedded.org Date: Thu, 16 Oct 2008 00:43:07 +0200 User-Agent: KMail/1.9.9 References: <200810151022.38477.zecke@selfish.org> <200810152153.52020.zecke@selfish.org> In-Reply-To: MIME-Version: 1.0 Message-Id: <200810160043.08202.zecke@selfish.org> X-Broken-Reverse-DNS: no host name found for IP address 92.116.127.219 Subject: Re: [RFC] Enable --hash-style=both for all recent gcc4 targets X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2008 22:48:22 -0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wednesday 15 October 2008 21:58:40 Koen Kooi wrote: > On 15-10-2008 21:53, Holger Freyther wrote: > > On Wednesday 15 October 2008 20:24:07 Koen Kooi wrote: > >> I'm undecided about putting the linker stuff in angstrom.inc vs. > >> angstroom-.inc. Go for what you think is best :) > > > > Google couldn't tell me if uclibc supports GNU style hashes, so I only > > change eglibc and glibc... happy rebuilding and I'm sorry when I broke > > things. > > > > I decided to land now as PRs are changing all the time and keeping up > > with things is pretty hard... > > You did change a S-O-B to an A-B, which AIUI is not how it should work. > Time to update teh commit policy to include SOB and ABs? Wow, I had to read that a couple of times. In Linux terms I would have to add a S-O-B to the commit. If it goes through your hands you add your S-O-B as well, if you just review and like the patch you ack? yes, the policy needs update... and I will sleep now z.