> > Well l-o tree is short for the linux-omap tree. Then I have various > queues of stuff going into the mainline kernel: > > omap-fixes > omap-upstream > omap1-upstream > omap2-upstream > omap3-upstream > ... > > Out of these queues omap-fixes will be sent out as needed during the > -rc cycle, while omap*-upstream queues are stuff for the next merge > window. > > These branches show up at the git web interface at the bottom: > > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary > > Not that many patches in these queues right now, btw. > That's very helpful. Would you mind confirming/answering a few more questions? 1. Generally, are all fixes/changes that go to any of the queues headed to the mainline always pushed into the l-o tree? If not, why not? 2. How about the reverse - are all l-o fixes/changes eventually queued to mainline? Or is there certain l-o functionality that won't ever go to mainline? 3. By "merge window" do you mean times that you pull mainline updates down into l-o tree? Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
