On Tue, Jul 14, 2015 at 11:32:27AM -0400, Sasha Levin wrote:

Re-wrapped the text, it looks like something joined all the paragraphs
up into single lines.

> > If the issue being fixed is serious enough to take out substantial
> > portion of our test coverage or affect a lot of other development
> > usage then that's really disruptive to other work, it impacts things
> > like bisection for example.  A strong rule does nobody any good,
> > it's overkill for the problem.

> If there's an issue that causes that effect then the original commit that
> caused it should be reverted rather than introducing an untested fix right
> away.

> Obviously not a hard rule, but it should be the case in general.

That's still sending a change of course which was what was being
objected to.