From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: git@vger.kernel.org, rybak.a.v@gmail.com
Subject: Re: [PATCHv6 00/10] Reroll of sb/diff-color-move-more
Date: Thu, 19 Jul 2018 12:05:05 -0700 [thread overview]
Message-ID: <xmqqwotrdp26.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180718193156.47365-1-sbeller@google.com> (Stefan Beller's message of "Wed, 18 Jul 2018 12:31:46 -0700")
Stefan Beller <sbeller@google.com> writes:
> v6:
> * fixed issues hinted at by Andrei, thanks! (range-diff below)
> * incorporates the new config option, sent separately previously.
Let's declare victory and move to incremental by merging to 'next',
if nobody spots anything more serious than just a missing SP around
comparison operator.
prev parent reply other threads:[~2018-07-19 19:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 19:31 [PATCHv6 00/10] Reroll of sb/diff-color-move-more Stefan Beller
2018-07-18 19:31 ` [PATCH 01/10] xdiff/xdiff.h: remove unused flags Stefan Beller
2018-07-18 19:31 ` [PATCH 02/10] xdiff/xdiffi.c: remove unneeded function declarations Stefan Beller
2018-07-18 19:31 ` [PATCH 03/10] t4015: avoid git as a pipe input Stefan Beller
2018-07-18 19:31 ` [PATCH 04/10] diff.c: do not pass diff options as keydata to hashmap Stefan Beller
2018-07-18 19:31 ` [PATCH 05/10] diff.c: adjust hash function signature to match hashmap expectation Stefan Beller
2018-07-18 19:31 ` [PATCH 06/10] diff.c: add a blocks mode for moved code detection Stefan Beller
2018-07-18 19:31 ` [PATCH 07/10] diff.c: decouple white space treatment from move detection algorithm Stefan Beller
2018-07-18 19:31 ` [PATCH 08/10] diff.c: factor advance_or_nullify out of mark_color_as_moved Stefan Beller
2018-07-18 19:31 ` [PATCH 09/10] diff.c: add white space mode to move detection that allows indent changes Stefan Beller
2018-07-18 19:31 ` [PATCH 10/10] diff.c: offer config option to control ws handling in move detection Stefan Beller
2018-07-19 19:05 ` Junio C Hamano [this message]
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=xmqqwotrdp26.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rybak.a.v@gmail.com \
--cc=sbeller@google.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).