Hi, Looking at the linux-omap tree using the gitweb interface. Apart from the "master" branch and tags. why do we have lots of branches? How and when do they intertact with each other. 17 hours ago omap1-upstream shortlog | log | tree 17 hours ago omap2-upstream shortlog | log | tree 17 hours ago omap3-boards shortlog | log | tree 17 hours ago omap3-upstream shortlog | log | tree 17 hours ago omap4 shortlog | log | tree 17 hours ago pm shortlog | log | tree 19 hours ago omap-headers shortlog | log | tree 19 hours ago omap-upstream shortlog | log | tree 19 hours ago omap-fixes shortlog | log | tree 47 hours ago master shortlog | log | tree 2 weeks ago omap-decimate shortlog | log | tree 2 weeks ago omapfb-upstream shortlog | log | tree 2 weeks ago omap-pool shortlog | log | tree 3 weeks ago for-next-2.6.30 shortlog | log | tree 4 weeks ago for-next shortlog | log | tree 4 weeks ago iommu shortlog | log | tree 2 months ago omap-2.6.29 shortlog | log | tree 3 months ago clks-testing shortlog | log | tree 3 months ago delete shortlog | log | tree 4 months ago omap-2.6.28 shortlog | log | tree 4 months ago tidspbridge shortlog | log | tree 5 months ago dspgateway shortlog | log | tree 5 months ago linus shortlog | log | tree 6 months ago musb shortlog | log | tree Can anyone explain what exactly goes into each of them? Some are straight forward like pm, usb, tidspbridge, gateway. not sure about for-next-2.6.30, omap-fixes. Trying to understand things/mode of development in here. Thank you, Ryan -- 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
