bug-gawk
[Top][All Lists]
Advanced

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

Re: Codespell report for "gawk" (on fossies.org)


From: Fossies Administrator
Subject: Re: Codespell report for "gawk" (on fossies.org)
Date: Wed, 15 Jan 2020 10:49:55 +0100 (CET)
User-agent: Alpine 2.21 (LSU 202 2017-01-01)

Hi Arnold,

Is there some way I can dynamically request a run, e.g. by uploading
a tar ball, or by plugging in a git URL so that it would run on
the master branch of the gawk repo?

You cannot force directly such a run by yourself but ...

Or by mailing the URL of a tarball to an address? (The latter is how the translation project works.)

... yes, you can send a short mail to <address@hidden> with the URL of a tarball to be checked (don't hesitate to do that multiple times).

The more I look at the report, the cooler I think this is.

Oh, I'm very pleased to hear that.

Regards

Jens

Fossies Administrator <address@hidden> wrote:

Hi "gawk"-team,

the FOSS server fossies.org - also supporting "gawk" - 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 (for testing purposes) an analysis for
the current "gawk" release 5.0.1:

  https://fossies.org/linux/misc/gawk/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/gawk-5.0.1.tar.xz/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/gawk/codespell_conf.html

showing some used "codespell" configurations and

  https://fossies.org/linux/misc/gawk/codespell_fps.html

showing all resulting obvious "false positives".

Although many of the found errors are in ChangeLog files or a "test"
directory I hope that the report can be nevertheless a little bit helpful.

If appropriate, additional reports for the current or future development
versions could be created (but in a special "test" folder that isn't
integrated in the Fossies standard services and should - at least
principally - also not be accessible by search engines).

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]