git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2018, #03; Wed, 23)
Date: Thu, 24 May 2018 12:09:21 -0700	[thread overview]
Message-ID: <CAGZ79kag9m02xtJKg05aPE4Grq2wBWSmUr3JdwfyHsMawR7m5Q@mail.gmail.com> (raw)
In-Reply-To: <xmqqwovtudia.fsf@gitster-ct.c.googlers.com>

> * sb/diff-color-move-more (2018-05-21) 8 commits
>  - diff: color-moved white space handling options imply color-moved
>  - diff.c: add --color-moved-ignore-space-delta option
>  - diff.c: decouple white space treatment from move detection algorithm
>  - diff.c: add a blocks mode for moved code detection
>  - diff.c: adjust hash function signature to match hashmap expectation
>  - diff.c: do not pass diff options as keydata to hashmap
>  - xdiff/xdiffi.c: remove unneeded function declarations
>  - xdiff/xdiff.h: remove unused flags
>
>  "git diff --color-moved" feature has further been tweaked.
>
>  Will merge to 'next'.

This is nowhere near done after reading the feedback from
Jonathan Tan; I am considering redoing it completely differently.

Please eject from next. (at least the last 3 patches, the patches
up to "add blocks mode" are reasonable.)

  parent reply	other threads:[~2018-05-24 19:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24  0:02 What's cooking in git.git (May 2018, #03; Wed, 23) Junio C Hamano
2018-05-24  6:39 ` Elijah Newren
2018-05-28  5:34   ` Junio C Hamano
2018-05-24 19:09 ` Stefan Beller [this message]
2018-05-24 19:42 ` Ævar Arnfjörð Bjarmason
2018-05-24 19:50 ` Luke Diamand
2018-05-25 12:31 ` js/empty-config-section-fix, was " Johannes Schindelin
2018-05-28  5:40   ` Junio C Hamano
2018-05-28 11:20     ` Johannes Schindelin
2018-05-29 16:49       ` Jeff King

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=CAGZ79kag9m02xtJKg05aPE4Grq2wBWSmUr3JdwfyHsMawR7m5Q@mail.gmail.com \
    --to=sbeller@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).