lkml.org 
[lkml]   [2016]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [tip:perf/core] perf/x86: Move perf_event.c ............... => x86/events/core.c
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@suse.de>
> > AuthorDate: Mon, 8 Feb 2016 17:09:04 +0100
> > Committer: Ingo Molnar <mingo@kernel.org>
> > 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

\
 
 \ /
  Last update: 2016-02-09 15:21    [W:0.076 / U:26.588 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site