On Wednesday 03 October 2012 14:08:16 McClintock Matthew-B29882 wrote: > On Wed, Oct 3, 2012 at 8:43 AM, Paul Eggleton > > <[email protected]> wrote: > > The answer is no, it doesn't. > > > > I guess on reflection we probably ought to be consistent here though - for > > better or worse, this is not what has been done when pulling in recipes > > from OE-Classic for the rest of meta-openembedded. The commit message > > does already list the changes from the original, and I'll concede that > > having just one revision doesn't give a huge amount in the way of insight > > on previous origin; ultimately as you say, OE-Classic is still there as a > > reference for that. > > > > OK, I've squashed those commits out on the branch. Would it be worth me > > posting a v2 after all these changes? > > Actually, this is one really annoying thing about OE. When people > rename the file 'git blame' comes worthless. Is there a way around > this?
Usually it picks up on renames just fine, but as with git diff -M there is some fuzziness in how it determines the difference between a file rename and an unrelated delete followed by an add; sometimes the difference is too great for git to consider as a rename with its default settings. I just tested, you can improve rename detection with git blame by using the -C option though; adjusting the -M value might also help. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
