Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 3.4k
    • Issues 3.4k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1.1k
    • Merge requests 1.1k
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Admin message

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • MesaMesa
  • mesamesa
  • Issues
  • #4742

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

The FOSS server fossies.org - supporting also the mesa project - offers among others a feature named "Source code misspelling reports". Such reports are normally only generated on request, but as Fossies administrator I have just created for testing purposes such a codespell based analysis for the mesa GitLab "main" version:

 https://fossies.org/linux/test/mesa-main.tar.gz/codespell.html

That version independent URL hopefully always redirects to the report for the latest "main" version identified by the short GitLab commit ID and a year-month-day string (YYMMDD) representing the according git pull date (mostly = commit date). The data are residing within a special restricted "test" folder that isn't really integrated into the standard Fossies services and should also not be accessible to search engines. The report should be available at least for some weeks and is continuously updated (currently every four hours).

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 exclude them if applicable.

In particular, I also had trouble deciding which subdirectories should be excluded as external source code and which should not.

Errors without a determined context (marked by a "?") should be given special attention, as they may be contained in the source code itself. They are easy to find by sorting the spelling error context type by clicking the bold "T" in the column header (if JavaScript is enabled).

Just for information there are also three supplemental pages showing some used "codespell" configuration details, all obvious false positives and an misspelling history (log).

Ok, spelling corrections certainly have a low priority, but they may also contribute to the overall quality of a software project.

Edit: I just changed the cloned and analyzed repo from "master" to "main" (the new default). The originally given "master" URLs will still be reachable for a week; a significant difference is actually only the for "main" missing misspelling history of "master" that does not yet exist for "main" due to the changeover

Edited May 07, 2021 by jschleus
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking