Messages in this thread | | | Date | Tue, 8 Jan 2008 23:17:22 +0100 | From | Sam Ravnborg <> | Subject | Re: [PATCH 3/5] x86: coding style fixes in arch/x86/ia32/ia32_aout.c |
| |
> > 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
| |