Linus Torvalds writes: (Summary) wrote:
Honestly, I don't think we'd get the testing this kind of change needs except by just trying it.
except by just trying it.
I'm willing to merge this in the 4.17 merge window, with the understanding that if people end up reporting issues, we may just have to revert it all, and chalk it up to a learning experience - and add the appropriate commentary in the kernel code about exactly what it was that depended on that MONO/BOOT difference.
was that depended on that MONO/BOOT difference.
One non-technical thing I would ask: use some other word than "conflate". So "trying to conflate two issues" means "trying to mix two issues that are not the same into one".
are not the same into one".
So "unify" and "conflate" mean both the same thing and almost exactly the opposite at the same time.
the opposite at the same time.
And yes, you will find dictionaries (and linguists) that hold purely to the old meaning.
[...]
userspace folks to make a final decision.Honestly, I don't think we'd get the testing this kind of change needs except by just trying it.
except by just trying it.
I'm willing to merge this in the 4.17 merge window, with the understanding that if people end up reporting issues, we may just have to revert it all, and chalk it up to a learning experience - and add the appropriate commentary in the kernel code about exactly what it was that depended on that MONO/BOOT difference.
was that depended on that MONO/BOOT difference.
One non-technical thing I would ask: use some other word than "conflate". So "trying to conflate two issues" means "trying to mix two issues that are not the same into one".
are not the same into one".
So "unify" and "conflate" mean both the same thing and almost exactly the opposite at the same time.
the opposite at the same time.
And yes, you will find dictionaries (and linguists) that hold purely to the old meaning.