WIP: Bug 5021 - Add a script to fix spelling errors with codespell#562
WIP: Bug 5021 - Add a script to fix spelling errors with codespell#562mrumph wants to merge 3 commits intosquid-cache:masterfrom
Conversation
Run "scripts/spell-check.sh" from the Squid tree root directory. For details, see bug report 5021: - https://bugs.squid-cache.org/show_bug.cgi?id=5021 Changes to be committed: new file: scripts/codespell-whitelist.txt new file: scripts/spell-check.sh
Ran "scripts/spell-check.sh" from the Squid tree root directory. For details, see bug report 5021: - https://bugs.squid-cache.org/show_bug.cgi?id=5021
|
Can one of the admins verify this patch? |
You use a separate git branch for each PR/work. Git branches are "cheap". To untangle this, I suggest moving the first commit from your PR branch (i.e. 0678534) into a separate/new branch. The following worked in my tests (that are based on GitHints setup): You could repeat the above for the second commit (2c7a572), creating a new branch and PR, OR, if you prefer, you can delete the first commit from this PR branch. I think the former is easier, but I am not a git or GitHub guru. At any rate, do not worry about the current wrong PR state -- we can figure it out! |
| % vi /usr/local/squid/etc/squid.conf | ||
|
|
||
| 2. Initalise the cache: | ||
| 2. Initialise the cache: |
There was a problem hiding this comment.
@mrumph, is there a way to tell codespell to prefer one spelling over the other? This is not critical or even important, but most Squid sources use the (American) "initialize" variant rather than the (British) "initialise" variant. I do not think codespell should change one for the other (or, at the very least, that deserves a separate discussion that I do not want to have now/here), but when fixing a spelling mistake, can we tell codespell to use the prevailing (in Squid) variant?
$ git grep -i initialise | wc -l
88
$ git grep -i initialize | wc -l
416There was a problem hiding this comment.
One possibility (but not really desirable for a number of reasons) is to supply our own dictionary with the -D option on codespell.
There was a problem hiding this comment.
If that custom dictionary will replace the standard one (rather than just overwrite a few entries), then I agree that -D is not a good solution. Let's ignore this problem.
[Bug 5021] Add a script to fix spelling errors with codespell
Run "scripts/spell-check.sh" from the Squid tree root directory.
For details, see bug report 5021: