public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppluzhnikov at google dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/25337] Codespell report for glibc Date: Wed, 17 May 2023 15:41:11 +0000 [thread overview] Message-ID: <bug-25337-131-GbbuLCFwVw@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25337-131@http.sourceware.org/bugzilla/> 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. 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. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-17 15:41 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25337-131@http.sourceware.org/bugzilla/> 2023-05-15 0:06 ` ppluzhnikov at google dot com 2023-05-15 13:10 ` Jens.Schleusener at fossies dot org 2023-05-17 15:41 ` ppluzhnikov at google dot com [this message] 2023-05-18 14:54 ` Jens.Schleusener at fossies dot org 2023-05-23 3:29 ` cvs-commit at gcc dot gnu.org 2023-05-23 10:26 ` cvs-commit at gcc dot gnu.org 2023-05-23 11:59 ` cvs-commit at gcc dot gnu.org 2023-05-23 15:23 ` cvs-commit at gcc dot gnu.org 2023-05-23 16:24 ` cvs-commit at gcc dot gnu.org 2023-05-27 16:37 ` cvs-commit at gcc dot gnu.org 2023-05-27 20:45 ` cvs-commit at gcc dot gnu.org 2023-05-29 23:00 ` cvs-commit at gcc dot gnu.org 2023-05-30 23:07 ` cvs-commit at gcc dot gnu.org 2023-06-02 1:42 ` cvs-commit at gcc dot gnu.org 2023-06-02 23:50 ` cvs-commit at gcc dot gnu.org 2023-06-03 17:35 ` Jens.Schleusener at fossies dot org 2023-06-05 0:10 ` ppluzhnikov at google dot com 2023-06-19 22:00 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-25337-131-GbbuLCFwVw@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).