On Mon, Nov 6, 2017 at 4:57 PM, Uwe Kleine-König <uwe@xxxxxxxxxxxxxxxxx> wrote:
>
> Having said that I question if it is a good idea at all to provide a way
> to change the build without dirtying the working copy.
>
I think I am the one that introduce the local.mk. I can explain some of
my usage of it.
I think there are two kind of people.
1) people don't use local.mk. People like to keep the tree clean with
git etc. They don't have local.mk. This does not concern them.
2) People like me using the local.mk.
I mostly use local.mk for the rules that is
1) local. e.g. how many jobs to invoke when start building
2) rules that I need which is local and I need it for every git branch.
e.g. my rules for the stress test. I want to be able to run stress test
on each branch as needed. Those stress test has external reference
point to the Linux kernel compile results. It is not
suitable to check in
into git.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
