From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lo.gmane.org ([80.91.229.12]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1NSAq0-0002Tr-1Q for openembedded-devel@lists.openembedded.org; Tue, 05 Jan 2010 15:56:51 +0100 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NSAo1-0005QM-26 for openembedded-devel@lists.openembedded.org; Tue, 05 Jan 2010 15:54:45 +0100 Received: from p5b3b2efd.dip.t-dialin.net ([91.59.46.253]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2010 15:54:45 +0100 Received: from no2spam by p5b3b2efd.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 Jan 2010 15:54:45 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: openembedded-devel@lists.openembedded.org From: Rolf Leggewie Date: Tue, 05 Jan 2010 15:54:13 +0100 Message-ID: References: <201001040357.33204.holger+oe@freyther.de> <4B42044B.8050801@nospam.arcornews.de> <201001041639.52002.holger+oe@freyther.de> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p5b3b2efd.dip.t-dialin.net User-Agent: Thunderbird 2.0.0.23 (X11/20090817) In-Reply-To: <201001041639.52002.holger+oe@freyther.de> Sender: news X-SA-Exim-Connect-IP: 80.91.229.12 X-SA-Exim-Mail-From: gcho-openembedded-devel@m.gmane.org X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: No (on linuxtogo.org); Unknown failure Subject: Re: why we don't setup a buildbot for openembedded QA? 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: Tue, 05 Jan 2010 14:56:51 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Holger Hans Peter Freyther wrote: > Oh My God. Thanks so much! The last time we talked you had some issues with > the update and said it would not work properly. I think the credit goes to Jeremy for resolving the issue upstream. I only reported it to him and did the packaging. I was sure I informed you about the update but it looks like I didn't. I'm sorry about creating unnecessary double-work.