From: Elijah Newren <newren@gmail.com>
To: Fossies Administrator <Jens.Schleusener@fossies.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Some misspelling errors in the git release 2.24.0
Date: Wed, 6 Nov 2019 20:46:09 -0800 [thread overview]
Message-ID: <CABPp-BH=XxwJod8XpXYzpmXuo2-8LBozQGH4eEps_r4C798+ag@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1911061026130.15790@fossies.org>
On Wed, Nov 6, 2019 at 3:08 AM Fossies Administrator
<Jens.Schleusener@fossies.org> wrote:
>
> Hi Elijah,
>
> > On Mon, Nov 4, 2019 at 8:14 AM Fossies Administrator <Jens.Schleusener@fossies.org> wrote:
> >>
> >> Hi Elijah,
> >>
> >>> On Mon, Nov 4, 2019 at 7:07 AM Fossies Administrator
> >>> <Jens.Schleusener@fossies.org> wrote:
> > So, I used your codespell program
>
> That seems to be a misunderstanding: I'm not the author of the codespell
> program but I only use that program to detect spelling errors and point to
> their existence while offering the option to inspect the context of the
> probably misspelled words in a fast and comfortable way via a Web page.
Oops, sorry for the misunderstanding; thanks for clearing it up.
[...]
> Some of the according FPs are excluded by Fossies generally, some other
> obvious FPs are excluded by Fossies specifically for each FOSS project
> (see always the bold item "Codespell configuration" with a link to
> "Project-specific additions" or to "(no project-specific adaptions yet
> done)" that shows all the excluded words and directories/files).
[...]
> As one can see on the page
>
> https://fossies.org/linux/misc/git-2.24.0.tar.xz/codespell_conf_info.html
>
> there are already done some according attempts.
Ah, thanks for the pointer. Could you add t/t9150/svk-merge.dump and
t/t9151/svn-mergeinfo.dump the the list of files to exclude? Both
have the 'hapenning' typo, but both are a dump of some repository and
editing it means recomputing sha1sums and whatnot for tests that just
isn't worth it. I thought maybe I could get away with correcting
those spelling errors but backed out once I saw further knock-on
effects.
Thanks for the report and the background and corrections!
Elijah
next prev parent reply other threads:[~2019-11-07 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 14:55 Some misspelling errors in the git release 2.24.0 Fossies Administrator
2019-11-04 15:26 ` Elijah Newren
2019-11-04 16:14 ` Fossies Administrator
[not found] ` <20191105171107.27379-1-newren@gmail.com>
2019-11-05 18:24 ` Elijah Newren
2019-11-06 11:08 ` Fossies Administrator
2019-11-07 4:46 ` Elijah Newren [this message]
2019-11-07 9:18 ` Fossies Administrator
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABPp-BH=XxwJod8XpXYzpmXuo2-8LBozQGH4eEps_r4C798+ag@mail.gmail.com' \
--to=newren@gmail.com \
--cc=Jens.Schleusener@fossies.org \
--cc=git@vger.kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).