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

[PATCH 0/5] merge-tree fix-ups

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 26, 2012, 23:03 UTC
Message-ID
<1356563020-13919-1-git-send-email-gitster@pobox.com>

This is a small preparatory step to build a new merge strategy based on the disused merge-tree proof-of-concept code. It starts with a small set of code clean-up patches and ends with two bugfixes, at least for now.

Junio C Hamano (5):
  Which merge_file() function do you mean?
  merge-tree: lose unused "flags" from merge_list
  merge-tree: lose unused "resolve_directories"
  merge-tree: add comments to clarify what these functions are doing
  merge-tree: fix d/f conflicts
 Makefile              |   2 +-
 builtin/merge-index.c |   4 +-
 builtin/merge-tree.c  |  92 +++++++++++++++++++++++--------------
 merge-blobs.c         | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++
 merge-blobs.h         |   8 ++++
 merge-file.c          | 124 --------------------------------------------------
 merge-file.h          |   7 ---
 merge-recursive.c     |   6 +--
 t/t4300-merge-tree.sh |  44 ++++++++++++++++++
 9 files changed, 239 insertions(+), 172 deletions(-)
 create mode 100644 merge-blobs.c
 create mode 100644 merge-blobs.h
 delete mode 100644 merge-file.c
 delete mode 100644 merge-file.h
-- 
1.8.1.rc3.356.g686f81c
Next: Junio C Hamano
Message 1 of 6 in “merge-tree fix-ups”
  1. 0/5 merge-tree fix-upsJunio C Hamano, Dec 26, 2012
  2. 1/5 Which merge_file() function do you mean?Junio C Hamano, Dec 26, 2012
  3. 2/5 merge-tree: lose unused "flags" from merge_listJunio C Hamano, Dec 26, 2012
  4. 3/5 merge-tree: lose unused "resolve_directories"Junio C Hamano, Dec 26, 2012
  5. 4/5 merge-tree: add comments to clarify what these functions are doingJunio C Hamano, Dec 26, 2012
  6. 5/5 merge-tree: fix d/f conflictsJunio C Hamano, Dec 26, 2012

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.