On Thu, Apr 8, 2010 at 9:04 AM, vorad <vorad.1...@gmail.com> wrote: > Hi guys, > > I am wondering how are you rebasing against linux-next each day, given the > fact that the code is so rapidly changing. > Is there any guide on how we should do this? I only know about this one > (http://lwn.net/Articles/289245/ ) which I am not sure it's still up to date > with the latest changes. > > Thank you!
Why would you try? I think most work with a stable version, then rebase to a late rc release where things are relatively stable and do your final testing. Then submit it to a maintainer so they can get it into the next merge window. Thus most of your submissions to a maintainer should come at the end of a rc series, not during the highly crazy merge window. That window is more for the maintainers to push collections of patches to Linus. Then there is a month or two to work and any issues that crop up due to conflicting patches pushed during the merge and it all starts over again. Greg -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
