From: Morten Welinder <mwelinder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Kevin <ikke@ikke.info>, git <git@vger.kernel.org>
Subject: Re: Fwd: possible Improving diff algoritm
Date: Wed, 12 Dec 2012 16:40:32 -0500 [thread overview]
Message-ID: <CANv4PNm45xGBn2veKi1o0wB4K9NgsbtCsiymHNO4xbCDpJ5tDg@mail.gmail.com> (raw)
In-Reply-To: <7vvcc73yzh.fsf@alter.siamese.dyndns.org>
> So I think with s/Regularly/About half the time/, your observation
> above is correct.
>
> I think the reason you perceived this as "Regularly" is that you do
> not notice nor appreciate it when things go right (half the time),
> but you tend to notice and remember only when a wrong side happened
> to have been picked (the other half).
Is there a reason why picking among the choices in a sliding window
must be contents neutral?
I see these "illogical" (== stylistically not matching user intent) diffs
quite often. C comments (as in the example given) and #ifdef blocks
are typical cases.
Purely anecdotically, I have seen more trouble applying "illogical"
diffs than I would have expected from the corresponding "logical" diffs.
Morten
next prev parent reply other threads:[~2012-12-12 21:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO54GHC4AXQO1MbU2qXMdcDO5mtUFhrXfXND5evc93kQhNfCrw@mail.gmail.com>
2012-12-12 15:03 ` Fwd: possible Improving diff algoritm Kevin
2012-12-12 18:29 ` Junio C Hamano
2012-12-12 18:48 ` Brian J. Murrell
2012-12-12 19:30 ` Kevin
2012-12-12 20:29 ` Junio C Hamano
2012-12-12 21:40 ` Morten Welinder [this message]
2012-12-12 21:53 ` Junio C Hamano
2012-12-12 22:34 ` Andrew Ardill
2012-12-12 23:32 ` Javier Domingo
2012-12-12 23:43 ` Junio C Hamano
2012-12-12 23:49 ` Javier Domingo
2012-12-13 0:00 ` Michael Haggerty
2012-12-13 1:55 ` Morten Welinder
2012-12-13 4:58 ` Geert Bosch
2012-12-13 6:26 ` Junio C Hamano
2012-12-14 12:20 ` Javier Domingo
2012-12-14 22:29 ` Bernhard R. Link
2012-12-15 12:16 ` Javier Domingo
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=CANv4PNm45xGBn2veKi1o0wB4K9NgsbtCsiymHNO4xbCDpJ5tDg@mail.gmail.com \
--to=mwelinder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ikke@ikke.info \
/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).