Hi Jens,
quite a nice service, thank you for all that work. It's awesome !
We are aware of codespell but so far only use it as a CI check for
Wget2[1]. We didn't bother to backport the script yet to Wget 1.x.
See [2] and [3].
Indeed we plan for a new release - so you put some pressure on us to
correct all those misspellings now :-)
We will not correct words in "ChangeLog", as this is automatically
generated from git commit messages. And we can't change git commit
messages as this would destroy history (blockchain, you know ;-)).
There is also m4/po.m4 that we won't change, as it is from gettext.
Regards, Tim
[1] https://gitlab.com/gnuwget/wget2
[2] https://gitlab.com/gnuwget/wget2/-/blob/master/contrib/spell-checker
[3] https://gitlab.com/gnuwget/wget2/-/blob/master/.gitlab-ci.yml#L74
On 2/20/20 11:19 AM, Fossies Administrator wrote:
Hi,
the FOSS server fossies.org - also supporting "Wget" - offers a new
feature "Source code misspelling reports":
https://fossies.org/features.html#codespell
Such reports are normally only generated on request, but as Fossies
administrator I have just created an analysis for the current "Wget"
release 1.20.3 (since a new release seems coming soon):
https://fossies.org/linux/www/wget/codespell.html
That version-independent (not linked) URL should redirect always to the
last report (if available), so currently to
https://fossies.org/linux/www/wget-1.20.3.tar.lz/codespell.html
Although after a first review some obviously wrong matches ("false
positives") are already filtered out (ignored) please inform me if you
find more of them so that I can force a new improved check if applicable.
Just for information there are also two supplemental pages
https://fossies.org/linux/misc/wget/codespell_conf.html
showing some used "codespell" configurations and
https://fossies.org/linux/misc/wget/codespell_fps.html
Although except for the "usual" errors in the ChangeLog file only few
and unspectacular errors are found I hope that the report can be
nevertheless a little bit helpful.
Regards
Jens