Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes: >> They distract us from the core changes and slows us down. It is OK >> to do them as totally unrelated clean-up changes long after the dust >> settles, but not entangled with the other more important changes >> like these patches. > > There's things I can eject from this series, but I don't really find it > to be "while at it" changes, I suspect what you're thinking of is > one/some of: > ... > Or maybe you're OK with topic(s) at large, i.e. "switch the default, > update the docs, make sure noone's left behind", but would just like it > done in more incremental steps? I said something on this in a separate thread. Let me look it up. * Updating the build procedure so that sha1dc is used by default everywhere is a good idea, but that is less urgent and should be done separately, preferrably long after the dust settles from the above.
