git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Nauwelaerts <mark.nauwelaerts@gmail.com>
To: git@vger.kernel.org
Cc: Mark Nauwelaerts <mnauw@users.sourceforge.net>
Subject: [PATCH 0/2] restore fast-export full filecopy detection
Date: Sun, 24 Dec 2017 11:52:07 +0100	[thread overview]
Message-ID: <1514112729-31647-1-git-send-email-mark.nauwelaerts@gmail.com> (raw)

From: Mark Nauwelaerts <mnauw@users.sourceforge.net>

When using fast-export/fast-import to interface/bridge with another VCS
that explicitly tracks copy/rename as metadata, fast-export's ability
to report filecopy/filerename is quite useful (if not essential).

There has been a fix in this area recently with as side-effect that
in some scenarios a filecopy is no longer reported as such.
These few patches provide an alternative fix for the original problem
while still retaining previous fast-export's filecopy reporting.

See patches for additional details and commit references.


Mark Nauwelaerts (2):
  fast-export: ensure proper order of modify, copy and rename entries
  fast-export: remove now obsolete filtering of modified files

 builtin/fast-export.c  | 60 +++++++++++++++++++++++---------------------------
 t/t9350-fast-export.sh |  2 +-
 2 files changed, 28 insertions(+), 34 deletions(-)

-- 
2.7.4


             reply	other threads:[~2017-12-24 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-24 10:52 Mark Nauwelaerts [this message]
2017-12-24 10:52 ` [PATCH 1/2] fast-export: ensure proper order of modify, copy and rename entries Mark Nauwelaerts
2017-12-24 10:52 ` [PATCH 2/2] fast-export: remove now obsolete filtering of modified files Mark Nauwelaerts
2018-01-07 16:56 ` [PATCH 0/2] restore fast-export full filecopy detection Mark Nauwelaerts

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=1514112729-31647-1-git-send-email-mark.nauwelaerts@gmail.com \
    --to=mark.nauwelaerts@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mnauw@users.sourceforge.net \
    /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).