git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCHv4 0/6] D/F conflict fixes

From
Elijah Newren <newren@gmail.com>
Date
Jul 9, 2010, 13:10 UTC
Message-ID
<1278681056-31460-1-git-send-email-newren@gmail.com>

This patch series fixes a number of spurious directory/file conflicts and associated bugs appearing in cherry-pick, rebase, merge, and fast-export. It also has a minor robustness improvement for fast-import. This series includes testsuite fixes for currently known failures in both t6020-merge-df.sh and t6035-merge-dir-to-symlink.sh.

Changes since the previous submission:
  * Addressed comments from Junio in the previous round.
Alexander Gladysh (1):
      Add a rename + D/F conflict testcase
Elijah Newren (5):
      Add additional testcases for D/F conflicts
      merge-recursive: Fix D/F conflicts
      merge_recursive: Fix renames across paths below D/F conflicts
      fast-export: Fix output order of D/F changes
      fast-import: Improve robustness when D->F changes provided in wrong order
 builtin/fast-export.c           |   29 ++++++++++
 fast-import.c                   |    8 +++
 merge-recursive.c               |  108 ++++++++++++++++++++++++++++++++-------
 t/t3509-cherry-pick-merge-df.sh |   35 +++++++++++++
 t/t6020-merge-df.sh             |    2 +-
 t/t6035-merge-dir-to-symlink.sh |   64 +++++++++++++++++++++--
 t/t9350-fast-export.sh          |   24 +++++++++
 7 files changed, 247 insertions(+), 23 deletions(-)
Next: Elijah Newren
Message 1 of 7 in “[PATCHv4 0/6] D/F conflict fixes”
  1. Elijah NewrenJul 9, 2010
  2. 1/6 Add additional testcases for D/F conflictsElijah Newren, Jul 9, 2010
  3. 2/6 Add a rename + D/F conflict testcaseElijah Newren, Jul 9, 2010
  4. 3/6 merge-recursive: Fix D/F conflictsElijah Newren, Jul 9, 2010
  5. 4/6 merge_recursive: Fix renames across paths below D/F conflictsElijah Newren, Jul 9, 2010
  6. 5/6 fast-export: Fix output order of D/F changesElijah Newren, Jul 9, 2010
  7. 6/6 fast-import: Improve robustness when D->F changes provided in wrong orderElijah Newren, Jul 9, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.