Xiangfu Liu wrote:
Hi Peter Chen
Peter Chen wrote:
Hi, all
I would like to manage android patch and normal kernel code at one
code base, as some customers would like to get the android patched
kernel, but some would like to get the non-android patched kernel.
It can be done by maintaining android patch folder at kernel root path,
But it will inconvenient for diff the code between local and database
like svn status, it will have lots of M, but in fact, you only change
one file.
Any suggestions is welcome
1. since the kernel use "git". you can use different branch to maintain
the kernel.
then cherry-pick to your local upstream branch
2. try use "stGIT" to maintain the patches. ( that is what I use everyday)
for example: you only want file "a.c" goto "001-android.patch"
$ stg goto 001-android.patch && stg refresh a.c
then the a.c will merge to "001-android.patch". never touch other "M"
files
3. use "quilt" to maintain the patches.
Thank you!
Are there any ways to use SVN to do it? As our whole BSP is managed by
SVN, including u-boot, kernel, rootfs, etc.
Thank you!
--
Best regards,
Peter Chen
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
