Hi, Newly converted git user here. I've stopped working with Subversion ever since working with the Linux kernel has introduced me to git, and never looked back! I am currently working on a project in which I'm trying to backport the powerpc boot-wrapper and device tree handling from Linux 2.6.30 into Linux 2.6.21. We have some third party vendor code that is not ready for the (new) completely fair scheduler just yet. Yet, our BSP relies on cuImage and the DTS files. The approach I'm taking is to try to cherry-pick any commits between v2.6.21 and v2.6.30 on the Linux kernel git repository that touch any file in the arch/powerpc/boot directory into a v2.6.21 branch (and pray that the conflicts are manageable). I've tried something along these lines: git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 cd linux-2.6 git checkout -b mybranch v2.6.21 git format-patch -o patches v2.6.21..v2.6.30 arch/powerpc/boot git am -3 patches/* But, to my dismay, format-patch here tears apart the commits and applies ONLY the hunks that apply to the arch/powerpc/boot directory. What I'd much rather do is obtain a list of commits that apply to arch/powerpc/boot; but, then apply the entire patch. I'm a bit lost at how to proceed at this point? Do I need to write my own script that uses git-log to grab the commit hashes that I want, then call format-patch (or diff/apply/etc) individually on each of them? I realize I'll have to handle patch numbering myself, if I were to do that (luckily, I believe format-patch allows you to specify the starting number). I also know at some point, I'll have to drill down into individual commits and do some more detailed cherry picking to form the desired patch series. This script seems like a good deal of work for me... so before I go off and start it, I was wondering if the git gurus have any clever solutions for me? Thanks, Tommy Wang -- 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