On 6/2/26 09:38, Michael S. Tsirkin wrote:
But if as a project we want to limit the
blast-radius if we find we have to rip out a hypothetical tainted
contribution, shouldn't that mean that we hold that as a project-wide
line, rather than leaving it up to the opinion of the individual
maintainer ?

It's not clear it's practical anyway. So we limit contributions to 20+
lines, so what did we achieve? They accumulate over time.
For small contributions it's more likely that there's essentially one way to do them, therefore any copyright violation accusations would be more easily defensible. Also it's not like you'd rip out *all* small contributions at once, so it doesn't matter if they accumulate.

But yeah, it's possible to game the system by having many small contributions, which is why the policy tells you to contact the maintainer prior to sending many small fixes.

Paolo

Reply via email to