The files in `configs/` are defconfigs to build-test certain
features or feature combinations.

If you really want to add full configs, they should be checked
too. Even if not build tested, they'd need to be constantly
updated, e.g. when config complains about missing/unknown
symbols. But I don't think it would scale. If every Kconfig
symbol is stored in multiple configs, a tiny Kconfig change
would result in many manually updates for checked in configs.

I would prefer to only check defconfigs in. If it's not for
build testing but really to store a specfic config, one can
restore the full config using the commit that introduced
the defconfig. The same information would be stored, just
harder to check out but much easier to maintain.

View Change

To view, visit change 39900. To unsubscribe, or for help writing mail filters, visit settings.