git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fossies Administrator <Jens.Schleusener@fossies.org>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Some misspelling errors in the git release 2.24.0
Date: Thu, 7 Nov 2019 10:18:26 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.21.1911071007260.10631@fossies.org> (raw)
In-Reply-To: <CABPp-BH=XxwJod8XpXYzpmXuo2-8LBozQGH4eEps_r4C798+ag@mail.gmail.com>

Hi Elijah,

On Wed, 6 Nov 2019, Elijah Newren wrote:

> 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.

Sure, done.

Principally test directories and files seem to be a "special" area
also for spelling checks.

> I thought maybe I could get away with correcting
> those spelling errors but backed out once I saw further knock-on
> effects.

That is one reason that only the developers should made such corrections.

> Thanks for the report and the background and corrections!

Regards

Jens

-- 
FOSSIES - The Fresh Open Source Software archive
mainly for Internet, Engineering and Science
https://fossies.org/

      reply	other threads:[~2019-11-07  9:18 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
2019-11-07  9:18           ` Fossies Administrator [this message]

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=alpine.LSU.2.21.1911071007260.10631@fossies.org \
    --to=jens.schleusener@fossies.org \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    /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.
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 NNTP newsgroup(s).