Fix typos found by codespell - #20910
DimitriPapadopoulos wants to merge 2 commits into
Conversation
0aad621 to
9afdbca
Compare
|
As a single PR I am concerned that this goes beyond the scope of |
25bcdd1 to
7142654
Compare
|
I will sign the CLA if requested. |
|
While all the changes in this are individually trivial, collectively there is a lot of change going on. I think a CLA would be a good idea. Please submit one: |
7142654 to
0468892
Compare
|
ICLA signed and sent by mail. |
|
Could you please also split out the changes in the manual pages to a separate PR as I think we should backport these fixes to 3.1 and 3.0 branches. |
|
@t8m So you suggest a separate PR for |
|
Just |
|
Closed / reopened to remove the |
|
Changes in |
86a5fe0 to
7ff9a08
Compare
7ff9a08 to
3ba27bd
Compare
|
Please don't force push updates. We're prefer fixup commits. |
|
I have to force push anyway when rebasing:
But I get it, rebasing against master is one thing, force pushing my own changes is another thing. |
|
Rebase only if there is a conflict that needs to be resolved. Otherwise there is no point in rebasing except for cases where the PR is getting really old - i.e. more than half a year or so. |
Typos in doc/man* will be fixed in a different commit.
3ba27bd to
481fa14
Compare
|
24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually. |
|
Merged, thanks for the contribution. |
Typos in doc/man* will be fixed in a different commit. Reviewed-by: Tomas Mraz <[email protected]> Reviewed-by: Paul Dale <[email protected]> (Merged from #20910)
CLA: trivial
While I have modified many files, this is a trivial merge request in the sense that this is codespell fixing typos semi-automatically.
I have not modified the sacrosanct
LICENSE.txt.I have modified
CHANGES.mdandNEWS.md, some projects would rather not modify these files when they are directly generated from SCV messages, but I looks like it is not the case here.I have mostly modified documentation and code comments. There are two occurrences of misspelling a variable name, but the impact is very local, inside a source file.
Might overlap #16712. If you merge #16712, I will rebase to fix remaining typos.
Checklist