[16517] in Kerberos-V5-bugs

home help back first fref pref prev next nref lref last post

Re: [krbdev.mit.edu #8891] Codespell report for "krb5" (on

daemon@ATHENA.MIT.EDU (Fossies Administrator via RT)
Tue Mar 31 04:36:50 2020

From: "Fossies Administrator via RT" <rt@KRBDEV-PROD-APP-1.mit.edu>
In-Reply-To: <alpine.LSU.2.21.2003311019360.23363@fossies.org>
Message-ID: <rt-4.4.4-125197-1585643801-1500.8891-5-0@mit.edu>
To: "AdminCc of krbdev.mit.edu Ticket #8891":;
Date: Tue, 31 Mar 2020 04:36:41 -0400
MIME-Version: 1.0
Reply-To: rt@KRBDEV-PROD-APP-1.mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu


<URL: https://krbdev.mit.edu/rt/Ticket/Display.html?id=8891 >

Hi Greg,

> On Thu Mar 26 11:40:12 2020, Jens.Schleusener@fossies.org wrote:
>
>  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 force a new improved check if applicable.
>
> I found two false positives, although neither of them seems easy to filter for:
>
> * "Sorce" in README is a person's last name, not a typo for "Source".
> * "thur" in getdate.y is an abbreviation for "thursday", not a typo for
> "their".

Oops, that are two false positives that I try to avoid but ...

Now corrected.

> This may be an unusual property of the MIT krb5 project, but we ship a bunch of
> generated documentation in release tarballs that isn't checked into the
> repository. Many of the earlier results in the report are from the generated
> documentation, either mirroring a typo from elsewhere in the source code or
> simply reflecting a typo in some upstream material included by documentation
> tooling.

Yes, that is a general problem. If clearly to see I try to exclude such 
"external" or "third-party" sub-directories but often it's not so easy to 
decide. At least I exclude now "src/lib/crypto/builtin/aes/" although I 
have the impression that there are more directories to be excluded.

There are no "spectacular" errors and many of the found errors are "only" 
in comments and not "user visible". So ignore the irrelevant errors and 
take the report just as an information.

If at any time there is an interest to analyse a repository code so let it 
know me.

Regards

Jens

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

_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs

home help back first fref pref prev next nref lref last post