linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vince Weaver <vincent.weaver@maine.edu>
To: Ingo Molnar <mingo@kernel.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
	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, tglx@linutronix.de,
	linux-tip-commits@vger.kernel.org
Subject: Re: {SPAM?} Re: [tip:perf/core] perf/x86: Move perf_event.c ............... => x86/events/core.c
Date: Fri, 12 Feb 2016 17:12:32 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1602121709380.3656@macbook-air> (raw)
In-Reply-To: <20160209140551.GC26641@gmail.com>

On Tue, 9 Feb 2016, Ingo Molnar wrote:

> see for example how Git still knows that we had a 
> arch/x86/kernel/cpu/perf_counter.c initial file name.
> 
> Or how you did an optimization in c48b60538c3ba when the file was already named 
> cpu/perf_event.c! :-)

yes, for simple renames it works, but once files start getting 
"reorganized" and split up it gets tricky.  For example trying to track 
things across the single perf_event.h to the separate perf_event.h files
after the UAPI split is always a pain.

But anyway, it sounds like the renames are being done for reasonably good 
reasons, it's just the tip commit message that came my way didn't have 
this extra context.

Thanks,

Vince

  parent reply	other threads:[~2016-02-12 22:12 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
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         ` Vince Weaver [this message]
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.1602121709380.3656@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).