Re: {SPAM?} Re: [tip:perf/core] perf/x86: Move perf_event.c ............... => x86/events/core.c
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: {SPAM?} Re: [tip:perf/core] perf/x86: Move perf_event.c ............... => x86/events/core.c
- From: Vince Weaver <vincent.weaver@xxxxxxxxx>
- Date: Fri, 12 Feb 2016 17:12:32 -0500 (EST)
- Cc: Vince Weaver <vincent.weaver@xxxxxxxxx>, jolsa@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, bp@xxxxxxx, a.p.zijlstra@xxxxxxxxx, acme@xxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx, eranian@xxxxxxxxxx, peterz@xxxxxxxxxxxxx, hpa@xxxxxxxxx, tglx@xxxxxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20160209140551.GC26641@gmail.com>
- User-agent: Alpine 2.20 (DEB 67 2015-01-07)
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
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]