On Mon, Nov 06, 2017 at 09:57:23AM +0100, Uwe Kleine-König wrote: > Hello Luc, > > > -local.mk > > +.sparse.mk > > what is the motivation to hide this file? IMHO it is better to be aware > of eventual changes to the build system and so don't hide the file. > > 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 confess that this change is just for my own confort. I often need to change change the CFLAGS while debugging or profiling. I want that to be in a file, the file must of course not be under version control and like .bashrc, kernel's .config or GCC's generated .*.o.d files, I don't need to see this file and so I prefer it's an hidden one. I understand your worries but since it's a file purposely changed so that files are compiled differently, there is no surprises. For dirtying the build ... yes, something could be done but really, personnaly, I don't need this, I know when I need to clean my tree. Regards, -- Luc -- 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
