From: Jeff King <peff@peff.net>
To: Steven Drake <sdrake@xnet.co.nz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/1] Add commit log message spell checking feature.
Date: Sun, 28 Feb 2010 11:33:39 -0500 [thread overview]
Message-ID: <20100228163339.GA9399@coredump.intra.peff.net> (raw)
In-Reply-To: <7e21d6cd64aa088763c3ff11d6cbe78899ae7f10.1267314986.git.sdrake@xnet.co.nz>
On Sun, Feb 28, 2010 at 01:03:00PM +1300, Steven Drake wrote:
> Add 'git commit --spell' to run a spell checker on commit log message.
> The `commit.spell` configuration variable can be used to enable the spell
> checker by default and can be turned off by '--no-spell'.
Isn't this exactly the sort of thing the commit-msg hook is for? Though
personally I would probably just invoke interactive spell-checking from
the editor.
-Peff
next prev parent reply other threads:[~2010-02-28 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 0:01 Commit log message typos and spell mistakes Steven Drake
2010-02-28 0:03 ` [PATCH 1/1] Add commit log message spell checking feature Steven Drake
2010-02-28 16:33 ` Jeff King [this message]
2010-03-03 6:50 ` Steven Drake
2010-03-03 14:45 ` Jeff King
2010-03-03 7:21 ` Steven Drake
2010-03-03 7:36 ` Teemu Likonen
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=20100228163339.GA9399@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=sdrake@xnet.co.nz \
/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).