Hi Elijah,
On Wed, 6 Nov 2019, Elijah Newren wrote:
On Wed, Nov 6, 2019 at 3:08 AM Fossies Administrator
<Jens.Schleusener@xxxxxxxxxxx> wrote:
Hi Elijah,
On Mon, Nov 4, 2019 at 8:14 AM Fossies Administrator <Jens.Schleusener@xxxxxxxxxxx> wrote:
Hi Elijah,
On Mon, Nov 4, 2019 at 7:07 AM Fossies Administrator
<Jens.Schleusener@xxxxxxxxxxx> 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/
