Re: [PATCH 3/5] x86: coding style fixes in arch/x86/ia32/ia32_aout.c

[Sam Ravnborg]

> > Most of these kernel changes would probably get in the way of real 
> > development, making patches reject that would otherwise apply.
> 
> I'm curious, in what way would they interfere?

Developer A work one some complicated stuff in foo.c which is
not yet -mm fooder.

Developer B submits and have applied a massive cleanup to some of the
files touced by Developer A's patch.

Developer A now needs to fix up his stuff.

Reminder: Not everyone writes their stuff in 48 hours before it
is lkml ready.

> 
> Firstly, anyone with a forked kernel with outstanding patches that are 
> not in x86.git only has themselves to blame. We want to actively 
> discourage forking and sitting on patches too long.

Curious - what is the purpose of the x86.git tree these days?

	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/