[Bug libc/25337] Codespell report for glibc

["Jens.Schleusener at fossies dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=25337

--- Comment #3 from Jens Schleusener <Jens.Schleusener at fossies dot org> ---
Hi Paul,

> https://sourceware.org/bugzilla/show_bug.cgi?id=25337
>
> Paul Pluzhnikov <ppluzhnikov at google dot com> changed:
>
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Status|NEW                         |ASSIGNED
>           Assignee|unassigned at sourceware dot org   |ppluzhnikov at google dot com
>
> --- Comment #2 from Paul Pluzhnikov <ppluzhnikov at google dot com> ---
> Jens,
>
> Thanks for the report. I am going to fix all the misspellings.

Oh, that are unexpected (good) news.

> I've browsed through the fossies.org site, but couldn't find a way to download
> the results in a tool-friendly way (e.g. something like a CSV file with
> misspelling,correction or a set of diffs, or something similar).
>
> Since fossies.org gives diffs, they must be generated somewhere.
>
> I could of course scrape the report and write my own program to fix them, that
> would replicate a lot of work that fossies have already done.

May be you have already seen

  https://fossies.org/features.html#codespell

containing a.o.

  A note: Fossies provides as an information only the source code spelling
  check reports with the special option to inspect the context of the
  probably misspelled words in a fast and comfortable way. However Fossies
  doesn't create for e.g. "diff"-like files usable by the "patch" command
  or even GitHub pull requests (PRs) since the risk is too high that something
  would be wrongly corrected (but here you may find some small codespell
  usage hints). Whether it's worth the effort to correct the misspelling
  errors manually is a decision of the respective project.

Three years ago I started to hack two scripts one that offers the found 
misspellings and asks the user if it should do the correction and another 
that just did all the corrections (via sed) but I scrapped the idea.

Some according hints you may find on the small page

  https://fossies.org/codespell_usage_hints.html

So you may start e.g. with the list that is offered via the link "list" 
in the line above the spelling errors, e.g. currently

  https://fossies.org/linux/misc/glibc-2.37.tar.xz/codespell.glibc-2.37.txt
 
https://fossies.org/linux/test/glibc-master.c93ee96.230517.tar.xz/codespell.glibc-master.c93ee96.230517.txt

If that all isn't constructive I could exceptionally as last resort try to 
do the corrections and to try creating patch files using the "diff" 
command or even build a corrected tar file. But that would be new to me 
and I must sure that there are no false positives (what isn't trivial).

Regards

Jens

-- 
You are receiving this mail because:
You are on the CC list for the bug.