Hi all,
I was looking at git.linaro.org and I'd like to propose some consistency in naming our git trees and in how we branch them. The main reason for this from my perspective is to make it easy to point someone from a partner team or from a partner''s customer to the git server and have them quickly figure out what they need to pull. Right now we have:
Generic Linaro Kernels:
kernel/linux-linaro-${version}
Freescale:
bsp/freescale/linux-2.6-imx.git bsp/freescale/linux-linaro-natty.git bsp/freescale/linux-meta-linaro-natty.git bsp/freescale/mx5-gpu.git bsp/freescale/mx5-vpu.git bsp/freescale/u-boot-linaro-natty.git
Samsung:
bsp/samsung/linux-linaro-2.6.39.git bsp/samsung/u-boot-insignal-dev.git bsp/samsung/u-boot.git
ST-E: bsp/st-ericsson/firmware-ux500.git bsp/st-ericsson/linux-2.6.34-ux500.git bsp/st-ericsson/linux-2.6.35-ux500.git bsp/st-ericsson/linux-2.6.38-snowball.git bsp/st-ericsson/linux-2.6.38-ux500.git bsp/st-ericsson/u-boot-ux500.git
TI: people/andygreen/kernel-tilt.git
Each of the trees have various tags and branches based on how each team and developer works and I don't want to ask folks to change what they are doing for their day to work. What I'd like to see is a a separate set of official trees that only get updated with bits that we are ready for non-Linaro developers to use, do not get rebased, and get tagged at the end of each monthly cycle. My proposal:
kernel/linux-linaro-$version with tags for each monthly release: v$version-$milestone-$buildcount kernel/linux-linaro-android-$version with tags for each monthly release: android-v$version-$milestone-$buildcount kernel/$soc/linux-linaro-$version with tags for each monthly release: $bsp-v$version-$milestone-$buildcount kernel/$soc/linux-linaro-android-$version with tags for each monthly release: $bsp-android-v$version-$milestone-$buildcount
Comments?
~Deepak