The android kernel repository does branch from vanilla kernel. If you use git merge-base, you will find android-2.6.29 branches from stock v2.6.29, and android-2.6.32 branches from v2.6.32 and then merged with v2.6.32.9. android-2.6.35 branches from 2.6.35-rc6 and merged with v2.6.35. Besides, you can find vanilla tag since v2.6.11 to v2.6.32.
This is not a secret. You just need to get familiar with git. On 9月11日, 下午10時01分, Scott W <[email protected]> wrote: > Thanks, Ashwan! > > I agree that this "diff against stock kernel" approach seems most > straightforward, and is likely the approach i will need to take. > > However, (directed toward any Google Android folks monitoring this) > this approach is risky and not deterministic for obvious reasons. It > would seem that this process would be lots easier if the Android Linux > kernel tree had a "stock kernel" branch so a git diff would be easy to > do. (Of course, it would be even better if this two branch approach > was accompanied by something in the Documentation/android.txt file > that said "To patch a 2.6.<nn> kernel with Android patches, do the > following ..." -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
