On 07/01/2011 08:14 PM, Somebody in the thread at some point said:
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?
It would be less ridiculous than issuing monthly tarballs for the kernel
case.
However if you follow this logic to its natural conclusion you end up
with a text file listing git repos and tags, maybe build config
filenames... that sounds better to me.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
