From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757128AbcBIOCO (ORCPT ); Tue, 9 Feb 2016 09:02:14 -0500 Received: from www.linutronix.de ([62.245.132.108]:40843 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753521AbcBIOCM (ORCPT ); Tue, 9 Feb 2016 09:02:12 -0500 Date: Tue, 9 Feb 2016 15:00:21 +0100 (CET) From: Thomas Gleixner To: Vince Weaver cc: jolsa@redhat.com, linux-kernel@vger.kernel.org, bp@suse.de, a.p.zijlstra@chello.nl, acme@redhat.com, torvalds@linux-foundation.org, eranian@google.com, peterz@infradead.org, hpa@zytor.com, mingo@kernel.org, linux-tip-commits@vger.kernel.org Subject: Re: [tip:perf/core] perf/x86: Move perf_event.c ............... => x86/events/core.c In-Reply-To: Message-ID: References: <1454947748-28629-2-git-send-email-bp@alien8.de> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > AuthorDate: Mon, 8 Feb 2016 17:09:04 +0100 > > Committer: Ingo Molnar > > 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