From: Yann Dirson <ydirson@free.fr>
To: git@vger.kernel.org
Subject: Re: Bulk move and some of its close relatives
Date: Wed, 27 Oct 2010 09:05:01 +0200 [thread overview]
Message-ID: <20101027090501.71980573@chalon.bertin.fr> (raw)
In-Reply-To: <20101026181314.GA5695@home.lan>
Oh, and another I forgot to mention is detection of bulk copies. It is
somewhat tricky: while --find-copies-harder will properly work in
combination with --detect-bulk-copies, for the standard case we will
need to use find-copies-harder for those cases where not all of the
copied files have been modified.
For this, maybe it could help to store the unmodified src files in a
separate list to avoid pref degradation for the common case (similar to
my plans to avoid the need of the i_am_not_single flag in the current
bulkmove series by using a separte list for dst files).
--
Yann
next prev parent reply other threads:[~2010-10-27 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 21:06 [PATCH v7 0/3] Detection of directory renames Yann Dirson
2010-10-23 21:07 ` [PATCH v7 1/3] Introduce bulk-move detection in diffcore Yann Dirson
2010-10-25 8:08 ` Junio C Hamano
2010-10-25 20:12 ` Yann Dirson
2010-10-26 18:13 ` Bulk move and some of its close relatives Yann Dirson
2010-10-27 7:05 ` Yann Dirson [this message]
2010-10-28 20:20 ` [PATCH v7 1/3] Introduce bulk-move detection in diffcore Junio C Hamano
2010-10-28 21:42 ` Yann Dirson
2010-10-23 21:07 ` [PATCH v7 2/3] Add testcases for the --detect-bulk-moves diffcore flag Yann Dirson
2010-10-23 21:07 ` [PATCH v7 3/3] [WIP] Allow hiding renames of individual files involved in a directory rename Yann Dirson
2010-10-24 21:10 ` [PATCH] [RFC] Add --detect-bulk-moves output to unidiff format 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101027090501.71980573@chalon.bertin.fr \
--to=ydirson@free.fr \
--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.
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 NNTP newsgroup(s).