I have a stack of 100 patches against 2.6.30. A lot of these got merged between 2.6.30-32. How can I tell which ones have been applied? It doesn't work to check if patch A has been applied to 2.6.32. Other patches may have been applied on top of patch A obscuring it. Once solution would be to rebase the patch stack forward one commit at a time. That solves the problem of later patches obscuring patch A. Is there a better way to do this? -- Jon Smirl jonsmirl@xxxxxxxxx -- 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