On Sun, 10 Jun 2012, Matthew Cengia <mattcen@gmail.com> wrote:
If I had to do something like this I think I'd create a git repository of the original codebase, make a commit, apply patch, make another commit, and then use git to search for changes. I don't know if this is suitable for you, but it's the easiest thing I can think of.
How would you do that exactly? The git grep command gives you a list of files matching a regex. But I could get that result by just applying the patch normally and running "grep -R". The problem is not just getting a list of changed files, it's extracting the patches for those files. In this case I'm working on the SE Linux policy patch for Fedora 17 which is 153,202 lines and 1335 files. Then after finding the files that are of interest I had to separate out the ~100 that were of note from the rest which isn't a trivial matter when you have a 153,202 line text file! Thanks Rodney for the reference to csplit. That is much more convenient than downloading a random Ruby file from the net. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/