From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michel (BusError) Date: Tue, 8 Apr 2008 23:28:05 +0100 Subject: [Buildroot] Hi There In-Reply-To: <012f01c899bf$242ab100$070514ac@atmel.com> References: <200804081340.13053.buildroot.atmel.com@pollet.net> <877if8jvjh.fsf@macbook.be.48ers.dk> <012f01c899bf$242ab100$070514ac@atmel.com> Message-ID: <200804082328.05294.buildroot.atmel.com@pollet.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Tuesday 08 April 2008, Ulf Samuelsson wrote: > > On the U-Boot patch, pls try to push the patch at the u-boot mailing list. > After spending years in Limbo, the patching process of U-Boot is > progressing at a a rapid pace and if the patch is OK, you > should get it into U-boot in notime.. Well for me this stuff is a mean to an end : getting a distribution for my project. I don't necessarily want to subscribe to a 'developer' mailing list everytime I have a oneliner on projects where /i'm not a developer/ -- I'm not really a developer even on buildroot, just trying to do something with it :-) So I'm trying to do the 'right thing' by pushing patches up, but I can't possibly follow thru all the ramifications. If these patches posted here are to be up in limbo with a "wrong address" tag, please tell me and I can keep them in my git tree, and forget about them. My assumption was that there was a system of 'layers' like with the kernel, were separate branches had 'sergeants' and were collating and pushing relevant patchsets to top maintainers. It seems this is not the case. Cheers, Michel