Hi Leo, Leo Famulari <l...@famulari.name> writes:
[...] >> So we'd have a .defconfig file which lists just what we chose >> differently from upstream Linux, and every kernel bump would be a matter >> of updating its hash, and rarely, perhaps enabling something not in the >> default config, which would be added to our defconfig file. > > How would we know if we want to deviate from the defaults, except by > going through the new configuration options? We have to know what the > options are in order to decide about them. It seems like the same amount > of work to me. We'd know when someone has a specific request and creates an issue/submits a patch for it. Otherwise I don't think the kernel maintainers should treat it differently from any software we package (and we don't go reading all the new build flags of things like 'mpv' every time we bump its version). It's nice if they have the bandwidth to go through reviewing all the new build options, but I don't think it should be required. It's more important to keep the kernel up to date, in my opinion. -- Thanks, Maxim
