linux-kernel - Re: [tip:perf/core] perf/x86: Move perf_event.c ............... => x86/events/core.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.11.1602091458330.25254@nanos>
Date:	Tue, 9 Feb 2016 15:00:21 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Vince Weaver <vincent.weaver@...ne.edu>
cc:	jolsa@...hat.com, linux-kernel@...r.kernel.org, bp@...e.de,
	a.p.zijlstra@...llo.nl, acme@...hat.com,
	torvalds@...ux-foundation.org, eranian@...gle.com,
	peterz@...radead.org, hpa@...or.com, mingo@...nel.org,
	linux-tip-commits@...r.kernel.org
Subject: Re: [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@...e.de>
> > AuthorDate: Mon, 8 Feb 2016 17:09:04 +0100
> > Committer:  Ingo Molnar <mingo@...nel.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