Hi, I'm rather new to this mailing list so I hope this is the right place for my question :-) We recently moved one of our projects over from SVN to git. This project is basically a Linux BSP for an ARM9 based processor using Kernel 2.6.22. For release we always generate 3 patches: - BSP patch - USB patch (since USB part is an external patch comming from a 3rd party) - WiFi patch (same as for USB) So my question is: What's the best way for handling this inside the git repository? IMHO it would make sense to have 3 branches (BSP, USB, WiFi) each based on unmodified 2.6.22 Kernel. USB and WiFi branch is used for generating the patch and for applying possible fixes. BSP branch for actual BSP related feature development and fixes. The changes in these branches are merged into the master branch which is used for compiling/testing the whole BSP. Is this a useful approach or are there other, better ways for generating the three patches and compiling testing the whole thing? Thanks! Christian. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html