From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Thu, 29 Jan 2009 17:03:20 +0100 Subject: [Buildroot] target/device/Atmel kernel patches In-Reply-To: (Ulf Samuelsson's message of "Thu\, 29 Jan 2009 16\:27\:10 +0100") References: <87ab9d4w6j.fsf@macbook.be.48ers.dk> <1233005366.2298.118.camel@elrond.atmel.com> <871vup4ul9.fsf@macbook.be.48ers.dk> <1233008389.2298.129.camel@elrond.atmel.com> <87vds114op.fsf@macbook.be.48ers.dk> <871vumtb1w.fsf@macbook.be.48ers.dk> Message-ID: <8763jyrtfb.fsf@macbook.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Ulf" == Ulf Samuelsson writes: >> We already have a situation where more than half the size of buildroot >> is patches, continuing to grow this is not a workable situation. >> Ulf> I agree with this, but the solution I want to see is that you Ulf> only keep the latest patches in the tree, Ulf> and as we introduce new kernel versions we Ulf> let older patches slip into the mirror server. I don't see why we the buildroot project should mirror random obsolete board patches? And again, things should get pushed upstream so we only carry patches for (not-yet-applied-upstream) bugfixes. Ulf> I just want them to build as long as possible. Why can't people just continue to use an old buildroot release or store their (project specific) board patches outside buildroot? >> If people want to use an old kernel they can maintain it outside of >> buildroot or in their local buildroot tree. Ulf> I want to give people the capability to build old kernel Ulf> with a new root fs. No problem if we make it possible to get the kernel from somewhere else (for most commercial projects probably a local cvs/svn/git/whatever repository). >> I do agree we should make it easier to build u-boot / linux from a >> non-mainline svn/git/whatever tree, that's something I will work on >> after the release. -- Bye, Peter Korsgaard