On Tue, 9 Feb 2016, Vince Weaver wrote: > On Tue, 9 Feb 2016, tip-bot for Borislav Petkov wrote: > > > Commit-ID: fa9cbf320e996eaa3d219344b6f7013b096cafd9 > > Gitweb: http://git.kernel.org/tip/fa9cbf320e996eaa3d219344b6f7013b096cafd9 > > Author: Borislav Petkov <bp@xxxxxxx> > > AuthorDate: Mon, 8 Feb 2016 17:09:04 +0100 > > Committer: Ingo Molnar <mingo@xxxxxxxxxx> > > CommitDate: Tue, 9 Feb 2016 10:23:49 +0100 > > > > perf/x86: Move perf_event.c ............... => x86/events/core.c > > > > Also, keep the churn at minimum by adjusting the include "perf_event.h" > > when each file gets moved. > > I have to admit I've been falling behind on my lkml reading, but is there > a good reason for moving all these files around? > > I'm often using "git blame" to track down when bugs are introduced, and > it's a big pain trying to do that across file moves like this. Although > that's maybe just due to difficiencies in my git usage skills. git blame still tells you which commit modified a particular line. That's not lost accross a file move. git log stops per default when a file moved, but you can tell it not to do so via "--follow". Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|