On Fri, Mar 31, 2017 at 12:49 PM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > > That being said, I do wish there is a way to figure out which patches > haven't changed in the new series. e.g. from V4 to V5, only a few patches > actually change. I can just focus on those changed one. I suppose I can > write a script to detect the same patch on different series. > BTW, I just add that feature to my patch series script. It has been working for me on the new llvm-fix series. For every patch in the new series, the script do "interdiff" with every patch on previous series and output the smallest diff. That usually nicely show the incremental change compare to previous series. For the case there is no change, just apply that patch because it is the same as the previous series, which I already apply and reviewed. This feature actually work out better than I expected. Even if I use git merge, I still need to find out exactly what change between two branch, which has rebased and different commit mixed. e.g. V4 and V6. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
