Hi, I was working to get OpenWrt running on a custom ARM board and of course had a git tree (in fact just some minor modifications on top of the vanilla, but i see no reason to use Quilt when there's a nice comfortable git repository) lying around. So i've set KERNEL_GIT_CLONE_URI accordingly and (after two minor bugs promptly fixed by jow (thanks again!)) had it compiled.
The problem is that it looks like it's a policy (and not a bug) to expect all OpenWrt-specific generic patches to be already applied to that tree (be it KERNEL_GIT_CLONE_URI or EXTERNAL_KERNEL_TREE). I can't see how a kernel developer can be comfortable with that as: 1. Usually kernel developers prefer either plain Git or StGit or TopGit and want to have a clean vanilla tree after their work and so would like to not depend on OpenWrt's Quilt system to have a custom kernel based on a downloaded tarball; 2. If having all OpenWrt's patches in that custom repo, one has to constantly rebase (one way or the other) and to also manually sync with the patches from OpenWrt's tree. Shouldn't the OpenWrt-specific patches be kept in OpenWrt and applied during the prepare stage as usual? Or what is the ideal workflow in your opinion? TIA -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
