----- Original message ----- > On Sat, Oct 23, 2010 at 1:24 AM, Arjan van de Ven > <[email protected]> wrote: > > > What would happen is that people would not CC meego-kernel. > > > > > > So meego-kernel would be isolated from the rest of kernel > development. > > > > meego-kernel (heck, MeeGo as project) is NOT for kernel development. > > I don't WANT meego-kernel to be CC'd on lkml submissions. Things need > to get > > hashed out on LKML first. > > THEN people who care about meego can ask for a backport. > > > > MeeGo is a distribution where we integrate things, not where kernel > code > > gets developed. > > Ah, I'm sorry, I thought _collaboration_ was an important part of MeeGo. It should be IMHO. How abt this: assume meego-community and meego-kernel as subscriber only. A guy who is interested in meego-community finds a problem and needs to loop in meego-kernel, should he first subscribe to meego- kernel before posting?
Kinda constrictin, aint it? Regards, Nishanth Menon _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
