From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] linux-advanced: remove unused ancient kernel versions
Date: Mon, 27 Jul 2009 13:55:03 +0200 [thread overview]
Message-ID: <87d47mpch4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <87a5b0800907270244h2172338aj7255258ef1fca9fd@mail.gmail.com> (Will Newton's message of "Mon\, 27 Jul 2009 10\:44\:39 +0100")
>>>>> "Will" == Will Newton <will.newton@gmail.com> writes:
hi,
>> ?Ulf> I have customers which are still on the 2.6.22 level.
>>
>> Good for them. They are presumably using a 2 year old BR snapshot
>> as well?
Will> What is the cost of keeping these options?
The explosion in config combinations - BR is plenty hard to test to any
sensible degree as it is already. We cannot keep on adding new
versions without removing something old. There's several places in BR
where we have to go through extra hoops to support both old and new
stuff, or where combinations noone ever tried breaks.
I think the only realistic option is to keep the number of
combinations down so the remaining options gets more testing.
Will> Userland and build infrastructure often moves much quicker than
Will> kernels and I often have to patch support for older kernels back into
Will> buildroot. It's not a big difficulty but if the cost of keeping the
Will> options is low I don't see what the gain is in removing them.
Notice that the advanced linux config has options for custom (free
form) versions, so you don't need to patch anything. In fact I think
we should remove all the presets as they are always out-of-date like I
mentioned the other day.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-07-27 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 19:08 [Buildroot] [git commit] linux-advanced: remove unused ancient kernel versions Peter Korsgaard
[not found] ` <4A6CBC18.1020507@atmel.com>
2009-07-26 20:39 ` Peter Korsgaard
2009-07-27 9:44 ` Will Newton
2009-07-27 11:55 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d47mpch4.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox