bug-gnunet
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Codespell report for "GNUnet" (on fossies.org)


From: Fossies Administrator
Subject: Codespell report for "GNUnet" (on fossies.org)
Date: Sun, 6 Sep 2020 20:53:45 +0200 (CEST)
User-agent: Alpine 2.21 (LSU 202 2017-01-01)

Hi "GNUnet"-team,

the FOSS server fossies.org - also supporting "GNUnet" - offers among others a feature named "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 (for testing purposes) such an analysis for the new "GNUnet" release:

 https://fossies.org/linux/misc/gnunet/codespell.html

That version-independent (not linked) URL should redirect always to the last report (if available), so currently to

 https://fossies.org/linux/misc/gnunet-0.13.3.tar.gz/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 three supplemental pages
 https://fossies.org/linux/misc/gnunet/codespell_conf.html
showing some used "codespell" configurations and
 https://fossies.org/linux/misc/gnunet/codespell_fps.html
showing all resulting obvious "false positives" and
 https://fossies.org/linux/misc/gnumet/codespell_hist.html
showing changes regarding found spelling errors compared to previous
analyzed versions.

At first glance, there doesn't seem to be a serious bug and most errors are "only" in code comments, but some errors are also contained in output strings and are so visible to users.

Although the correction of misspellings and typos has probably not a top priority, I hope that the report can nevertheless be a little bit useful.

Regards

Jens

--
FOSSIES - The Fresh Open Source Software archive
mainly for Internet, Engineering and Science
https://fossies.org/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]