From: "Deepak Barua" <dbbarua@gmail.com>
To: git@vger.kernel.org
Subject: Adding spell checker to GIT
Date: Tue, 5 Dec 2006 22:09:53 +0530 [thread overview]
Message-ID: <b5a19cd20612050839y30d06e3bk3a718ef29d0e9328@mail.gmail.com> (raw)
In-Reply-To: <b5a19cd20612050805x309d667eq649ba7ef1b8109b7@mail.gmail.com>
Hi Jakub & Johannes,
Thank you for your help i will consider
the precommit-hook.
Regards
Deepak
---------- Forwarded message ----------
From: Deepak Barua <dbbarua@gmail.com>
Date: Dec 5, 2006 9:35 PM
Subject: Adding spell checker to GIT
To: git@vger.kernel.org
Hi All,
I am just thought of a idea to integrate a spell checker with
git so that when we check in the code the code comments are spell
checked before being put into the tree,maybe have a optimized
dictionary search.
what about this...? is it appropriate ...?
Regards
Deepak
--
Code Code Code Away
--
next prev parent reply other threads:[~2006-12-05 16:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 16:05 Adding spell checker to GIT Deepak Barua
2006-12-05 16:12 ` Jakub Narebski
2006-12-05 16:13 ` Johannes Schindelin
2006-12-05 16:39 ` Deepak Barua [this message]
2006-12-05 17:08 ` Andreas Ericsson
[not found] ` <200612051726.kB5HQO2t015777@laptop13.inf.utfsm.cl>
2006-12-12 19:51 ` Deepak Barua
2006-12-12 20:27 ` Johannes Schindelin
[not found] ` <d22d265a0612130103o1efcbd87sb93be9c2dad71307@mail.gmail.com>
2006-12-13 10:25 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2006-12-26 12:02 Deepak Barua
2007-01-04 20:46 Deepak Barua
2007-01-05 20:49 ` Johannes Schindelin
2007-01-06 3:21 ` Deepak Barua
2007-01-16 16:10 ` Johannes Schindelin
2007-01-16 17:34 ` Deepak Barua
2007-01-25 14:36 ` Deepak Barua
2007-01-25 16:46 ` Johannes Schindelin
2007-01-26 7:22 ` Deepak Barua
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=b5a19cd20612050839y30d06e3bk3a718ef29d0e9328@mail.gmail.com \
--to=dbbarua@gmail.com \
--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.
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).