> On Sat, Jul 29, 2023 at 05:54:47PM +0800, Zhangjin Wu wrote: > > The 'defconfig' will only be triggered while there is no .config there, > > I do think it is important, at the first time of using nolibc, I > > directly run kernel but it fails for it has a manual defconfig > > requirement every time, so, I do think a default defconfig for kernel > > for the first run or after a mrproper is helpful, it doesn't modify any > > .config for there is no one there. > > On the opposite, that's yet another example of automatic stuff that for > me adds zero value and just doubts in the user's head: "is it safe to > call this with my own config or should I keep a safe copy of it?", > "what will it use for the config?", "will the arch be correct if my > current config references 32BIT and the generated default one switches > it to 64?" etc. > > Please let's not add unneeded dependencies and chaining. It does not > help and makes it harder to restart at one specific step, thus lowers > the overall value. > Ok, let's do subtraction, drop this one and the timeout two. Thanks, Zhangjin > Willy
