[lkml]   [2009]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-next: manual merge of the i2c tree with the arm-current tree
On Wed, May 06, 2009 at 10:31:38AM +0200, Jean Delvare wrote:
> I don't know exactly how defconfigs are handled, but I can imagine that
> the responsible developer is running "make oldconfig" on the system in
> question from times to times and copying the result back to the
> defconfig file. The purpose of updating defconfig files is to make
> configuration option renames transparent.

The big problem is that everyone 'make oldconfig' is done, the entire
config file essentially gets re-sorted into some other random order,
and the changes are massive.

If a platform maintainer does this, and the result is committed, and
some other person has done some small sed-based updates to the defconfigs,
the result is _total_ chaos.

That's why I'm arguing for my approach. That way, platform maintainers
stand a better chance of seeing what happens to their defconfig files
and there's a substantially better chance of some coordination of those
changes (that is if the arch maintainer is doing their job properly.)

Russell King
Linux kernel 2.6 ARM Linux -
maintainer of:

 \ /
  Last update: 2009-05-06 21:07    [W:0.053 / U:2.088 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site