From mboxrd@z Thu Jan 1 00:00:00 1970 From: David VomLehn Subject: Re: [PATCH 0/1] Embedded Maintainer(s), linux-embedded@vger list Date: Thu, 12 Jun 2008 14:11:04 -0700 Message-ID: <485190E8.80705@cisco.com> References: <1209577322.25560.402.camel@pmac.infradead.org> <200806102235.09598.rob@landley.net> <484F66F8.4020409@snapgear.com> <200806111941.51221.rob@landley.net> <20080612182529.GB7423@nibiru.local> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080612182529.GB7423@nibiru.local> DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1655; t=1213305077; x=1214169077; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dvomlehn@cisco.com; z=From:=20David=20VomLehn=20 |Subject:=20Re=3A=20[PATCH=200/1]=20Embedded=20Maintainer(s ),=20linux-embedded@vger=20list |Sender:=20; bh=nr7TyJet5eQN6SA6fCeoVnb6aY2bxtYJqga3pjRGsJs=; b=lBF3Ay9a9zZn2NWVI7JN2UnVSVBQRLXODw9xYLmnnnjumuuc08Gwvpevzc 4qW4Zga0Mw+CCezt7xqvMgQ/l1SPYdxobOMowX8huRCp4UZ4kRJIQno8Kxf3 xLdbvGUVWL; Sender: linux-embedded-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: weigelt@metux.de Cc: Linux Embedded Maillist Enrico Weigelt wrote: > * Rob Landley schrieb: > >> Cross compiling breaks stuff, yes. >> >> Most packages don't cross compile at all. Debian has somewhere north of >> 30,000 packages. Every project that does large scale cross compiling >> (buildroot, gentoo embedded, timesys making fedora cross compile, etc) tends >> to have about 200 packages that cross compile more or less easily, another >> 400 or so that can be made to cross compile with _lot_ of effort and a large >> enough rock, and then the project stalls at about that size. >> > > The problem is: most embedded projects don't make really general-purpose > fixes (instead strange things like hacking up autogenerated files), so > they can't feed back to upstream. > > IMHO, a huge waste of working time. > > Amen, brother. I'm fortunate in that I work for an organization that is quite good about enforcing code reviews, specifically, the QA organization is empowered to reject changes that do not have code review notes. I also have a fairly broad scope, so I'm in on code reviews for a number of open source components. At each such review, one of my criteria is whether the change is suitable for pushing back to the appropriate community. This is not necessarily a short-term way to make friends, but the long-term effects will be good both for the company and for the open source community in general. Now, if we can only get the time to actually push all the backlogged fixes out... -- David VomLehn, dvomlehn@cisco.com The opinions expressed herein are likely mine, but might not be my employer's...