From: "Célestin Matte" <celestin.matte@ensimag.fr>
To: Sarma Tangirala <vtangira@buffalo.edu>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Célestin Matte" <celestin.matte@ensimag.fr>,
git <git@vger.kernel.org>
Subject: Re: git diff bug?
Date: Mon, 10 Jun 2013 14:44:27 +0200 [thread overview]
Message-ID: <51B5CA2B.101@ensimag.fr> (raw)
In-Reply-To: <CANd8ic+6AtWgbK3S7DMkaOz7K9WJYdq8ozP9mesc-vJRhxLjqg@mail.gmail.com>
Le 07/06/2013 18:01, Sarma Tangirala a écrit :
> On Thu, Jun 6, 2013 at 6:17 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Célestin Matte <celestin.matte@ensimag.fr> writes:
>>
>
>> But for a two-endpoint diff Porcelain (not the plumbing diff-files,
>> diff-index and diff-tree), I do not think it is particularly a bad
>> idea to add such a "typo-detection" feature.
>
> I was wondering if this feature is going to be added and if I could
> try implementing it.
Since nobody answered you (publicly at least), I will try doing it myself:
I think the best thing to do if you want a feature to be added is to
come with a patch and request for comments on it. Then, people will
discuss it and decide whether it's worth adding it to git. So yes, you
can try implementing it - all work is welcome :)
--
Célestin Matte
next prev parent reply other threads:[~2013-06-10 12:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 21:26 git diff bug? Sarma Tangirala
2013-06-06 21:42 ` Célestin Matte
2013-06-06 22:17 ` Junio C Hamano
2013-06-07 16:01 ` Sarma Tangirala
2013-06-10 12:44 ` Célestin Matte [this message]
2013-06-10 14:41 ` Sarma Tangirala
-- strict thread matches above, loose matches on Subject: below --
2009-04-04 1:10 David Abrahams
2009-04-04 1:45 ` Jeff King
2009-04-04 1:52 ` Jeff King
2009-04-06 9:09 ` David Abrahams
2009-04-06 14:44 ` Michael J Gruber
2009-04-06 17:58 ` David Abrahams
2009-04-06 18:48 ` Jeff King
2009-04-06 15:53 ` Jeff King
2009-04-06 17:37 ` Matthieu Moy
2009-04-06 17:56 ` Junio C Hamano
2009-04-06 19:32 ` Matthieu Moy
2009-04-06 18:16 ` David Abrahams
2009-04-07 18:25 ` Antriksh Pany
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=51B5CA2B.101@ensimag.fr \
--to=celestin.matte@ensimag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vtangira@buffalo.edu \
/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).