Closed guimard closed 1 year ago
This patch has a bunch of bad corrections (many cases of "pruning" -> "prunning", when "pruning" is correct).
Skimming through further, it looks like maybe they were a side effect of global find and replace of "runing" -> "running" that got out of hand? But they're right at the top of the patch where they should have been seen and fixed quickly??
Many of the corrections look good, but the "prunning" problem makes me not trust this patch enough to just casually apply it without a careful line-by-line review
@elliefm This issue seems to be closed, Github did not close it because the patch was not applied to master branch.
There were a handful of "big spelling fixes" patches a few years ago; I think this issue/PR was maybe fixing stuff that had already been fixed on master but not on 3.0, and that's why it was only applied to 3.0?? Who knows... it was me that merged it, but I've long since forgotten! It looks like the first fix in #2790, "complient" -> "compliant", was fixed on master already in 2017, so I'm going to assume that that was the case, and that this can be closed.
@a-tze thanks for the bump :)
Hello,
here is a little patch that fixes some common spelling errors based on version 3.0.8 (reported by lintian).
Cheers, Xavier