On Sun, Mar 10, 2024 at 10:07:14PM +0900, Masahiro Yamada wrote: > On Thu, Mar 7, 2024 at 9:10 AM Elliott Mitchell <ehem+linux@xxxxxxx> wrote: > > > > On Wed, Mar 06, 2024 at 12:20:17AM +0900, Masahiro Yamada wrote: > > > > > I see no good reason to do this change. > > > > > > I will not take this series. > > > > Could I get you to provide further detail as to why you consider my > > reasons inadaquate? > > > > The distribution is well-known. I believe in-tree and out-of-tree build > > mechanisms being as possible to each other is a Good Thing. > > > > I guess I should also note, in the past (890676c65d699, 9da0763bdd825, > > likely others) nicer build output has been sufficient justification for > > changes. An effect of the series is a leading "./" will disappear from > > many files in full build output. As such this also matches that reason. > > It is ideal to in-tree and out-of-tree build mechanisms > look symmetrical (and perhaps could be achieved in a > different way), but your approach is not the direction > I want to go. I'm glad we're in agreement with the former. Do you have any guesses for when your approach to this will be visible? I suspect most approaches will eventually run into an issue with the current interpretation of $(srctree)/$(objtree). Unless you can ensure $(src)/$(obj) will never end up with absolute paths. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sigmsg@xxxxxxx PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
