From: Vince Weaver <vincent.weaver@maine.edu>
To: 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,
tglx@linutronix.de, vincent.weaver@maine.edu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf/x86: Move perf_event.c ............... => x86/events/core.c
Date: Tue, 9 Feb 2016 08:55:52 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.20.1602090854100.3069@macbook-air> (raw)
In-Reply-To: <tip-fa9cbf320e996eaa3d219344b6f7013b096cafd9@git.kernel.org>
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.
Vince
next prev parent reply other threads:[~2016-02-09 13:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 16:09 [PATCH 0/5] perf: Sanitize perf directory structure, p1 Borislav Petkov
2016-02-08 16:09 ` [PATCH 1/5] x86/events: Move perf_event.c Borislav Petkov
2016-02-09 12:17 ` [tip:perf/core] perf/x86: Move perf_event.c ............... => x86/events/core.c tip-bot for Borislav Petkov
2016-02-09 13:55 ` Vince Weaver [this message]
2016-02-09 14:00 ` Thomas Gleixner
2016-02-09 14:05 ` Ingo Molnar
2016-02-09 14:11 ` Borislav Petkov
2016-02-12 22:12 ` {SPAM?} " Vince Weaver
2016-02-08 16:09 ` [PATCH 2/5] x86/events: Move perf_event_amd.c Borislav Petkov
2016-02-09 12:17 ` [tip:perf/core] perf/x86: Move perf_event_amd.c ........... => x86/events/amd/core.c tip-bot for Borislav Petkov
2016-02-08 16:09 ` [PATCH 3/5] x86/events: Move perf_event_amd_ibs.c Borislav Petkov
2016-02-09 12:17 ` [tip:perf/core] perf/x86: Move perf_event_amd_ibs.c ....... => x86/events/amd/ibs.c tip-bot for Borislav Petkov
2016-02-08 16:09 ` [PATCH 4/5] x86/events: Move perf_event_amd_iommu.* Borislav Petkov
2016-02-09 12:18 ` [tip:perf/core] perf/x86: Move perf_event_amd_iommu.[ch] .. => x86/events/amd/iommu.[ch] tip-bot for Borislav Petkov
2016-02-08 16:09 ` [PATCH 5/5] x86/events: Move perf_event_amd_uncore.c Borislav Petkov
2016-02-09 12:18 ` [tip:perf/core] perf/x86: Move perf_event_amd_uncore.c .... => x86/events/amd/uncore.c tip-bot for Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1602090854100.3069@macbook-air \
--to=vincent.weaver@maine.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=bp@suse.de \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).