git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Yann Dirson <ydirson@altern.org>
To: git@vger.kernel.org
Cc: Yann Dirson <ydirson@altern.org>
Subject: [PATCH v5 0/4] Detection of directory renames
Date: Sat,  9 Oct 2010 23:31:31 +0200	[thread overview]
Message-ID: <1286659895-1813-1-git-send-email-ydirson@altern.org> (raw)

Evolutions from v4 to v5:

(Jonathan Nieder) use memcpy, not strncpy overkill
(Jonathan Nieder) split 2 funcs out of diffcore_bulk_renames
(Jonathan Nieder) more comments
(Jonathan Nieder) avoid allocating often-useless filespec too early
(Jonathan Nieder) split into new func
(Ævar Arnfjörð Bjarmason) convert C99 comments intended to stay to C89 ones

(Jonathan Nieder, Ævar Arnfjörð Bjarmason) reworked style of test script
(Jonathan Nieder, Sverre Rabbelier) use compare_diff_raw, not compare_diff_patch;
	anonymize hashes and scores
(Jonathan Nieder) use "git commit" in test instead of only plumbing, and use test_tick

listed a number of additional FIXME's
changed wording "factorization" -> "bulk move"
changed --detect-dir-renames to --detect-bulk-moves and
	--hide-dir-rename-details to --hide-bulk-move-details
first attempt at showing the "/*" suffix in bulk moves, for comment
stop maintaining testcases for --hide-bulk-move-details, I'm just keeping
	the patch adding the flag in sync with other code changes anyway.


Yann Dirson (4):
  Introduce bulk-move detection in diffcore.
  Add testcases for the --detect-bulk-moves diffcore flag.
  [RFC] Only show bulkmoves in output.
  [RFC] Allow hiding renames of individual files involved in a
    directory rename.

 diff-lib.c                       |    6 +-
 diff.c                           |   12 ++
 diff.h                           |    6 +
 diffcore-rename.c                |  349 +++++++++++++++++++++++++++++++++++++-
 diffcore.h                       |    1 +
 t/t4046-diff-rename-factorize.sh |  251 +++++++++++++++++++++++++++
 tree-diff.c                      |    4 +-
 7 files changed, 617 insertions(+), 12 deletions(-)
 create mode 100755 t/t4046-diff-rename-factorize.sh

-- 
1.7.2.3

             reply	other threads:[~2010-10-09 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-09 21:31 Yann Dirson [this message]
2010-10-09 21:31 ` [PATCH v5 1/4] Introduce bulk-move detection in diffcore Yann Dirson
2010-10-09 21:31   ` [PATCH v5 2/4] Add testcases for the --detect-bulk-moves diffcore flag Yann Dirson
2010-10-09 21:31     ` [PATCH v5 3/4] [RFC] Only show bulkmoves in output Yann Dirson
2010-10-09 21:31       ` [PATCH v5 4/4] [RFC] Allow hiding renames of individual files involved in a directory rename Yann Dirson
2010-10-10 12:39       ` [PATCH v5 3/4] [RFC] Only show bulkmoves in output Yann Dirson
2010-10-10 19:59         ` [PATCH 0/2] " Yann Dirson
2010-10-10 19:59           ` [PATCH 1/2] " Yann Dirson
2010-10-10 19:59             ` [PATCH 2/2] [RFC] Transfer special display of toplevel dir to display-time Yann Dirson

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=1286659895-1813-1-git-send-email-ydirson@altern.org \
    --to=ydirson@altern.org \
    --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.
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).