On Sun, Apr 10, 2011 at 08:08:18AM +0930, Rusty Russell wrote: > (BTW, is there a simple way of doing a git blame on an older version of > a particular file, when the first git blame refers to a refactoring > patch and you want to dig deeper?) Something like: 1. git blame <file> 2. notice the sha5 of the change you want to ignore. 3. git blame <sha5>^ -- <file> Cheers, Shaun _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
