On Mon, 2006-05-08 at 19:30 -0500, Josh Boyer wrote: > On Tue, 2006-05-09 at 04:35 +0530, Rahul Sundaram wrote: > > On Mon, 2006-05-08 at 18:57 -0400, Christopher Blizzard wrote: > > > We're going to need to do something similar for One Laptop at some > > > point, but I'm hoping that will just be a kernel variant, not an > > > entirely separate package. But we'll need some weird stuff in any case. > > > Compressing memory on the fly, odd memory management and VM stuff, etc. > > > > > > This is going to be more and more of a problem, not less. How do we get > > > bleeding edge features into the kernel without causing pain to our > > > kernel guys? Can we get the kernel guys to just start using an external > > > git repo for everything to start? (Are they already doing that now?) > > > Is there a way we can re-think our processes so that we can actually > > > make this easier for our kernel folks instead of making it harder? > > > > > > Does the kernel still use pristine source + patches, or are we just > > > using a random git tree? > > > > pristine source + patches. > > That's what's in CVS. I was talking with Jeremy about this on IRC this > past weekend. There are git trees inside of RH that the kernel > developers use, and patches are generated from that. Maybe not everyone > uses them, but the git trees do exist. I might have misspoke on that. Seems I misunderstood our IRC conversation. Or I'm just confused. josh
