git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Fossies Administrator <Jens.Schleusener@fossies.org>
To: git@vger.kernel.org
Subject: Some misspelling errors in the git release 2.24.0
Date: Mon, 4 Nov 2019 15:55:07 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.21.1911041316270.23271@fossies.org> (raw)

Hi,

although misspelling corrections are not the most exciting issues and the 
spelling errors are rarely true code bugs but mostly contained in the 
comments and documentation parts they correction may still improve the 
overall quality of a software project a little bit.

In this sense I created a code misspelling report for "git" using the 
program "codespell"

  https://fossies.org/linux/misc/git-2.24.0.tar.xz/codespell.html

or version independent

  https://fossies.org/linux/misc/git/codespell.html

The latter URL redirects always to the report of the last "git" release 
supported on Fossies (if such a report was requested resp. is existing).

Principally it's possible to make further runs not only on "git" releases 
but also within a separated test environment on master or branches. If you 
found FPs please inform me and I will rerun the analysis.

Regards

Jens

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

             reply	other threads:[~2019-11-04 15:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 14:55 Fossies Administrator [this message]
2019-11-04 15:26 ` Some misspelling errors in the git release 2.24.0 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

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=alpine.LSU.2.21.1911041316270.23271@fossies.org \
    --to=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).