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

[PATCH] Reference technical/trivial-merge.txt in git-read-tree documentation

From
Petr Baudis <pasky@suse.cz>
Date
Nov 11, 2005, 20:51 UTC
Message-ID
<20051111205140.5719.68724.stgit@machine.or.cz>

That file, with the so valuable (and so confusing) tables describing the precise resolution rules git-read-tree follows, silently sat in the corner and almost noone knew about it (well, I didn't, at least). This references it from the git-read-tree documentation, so that there is some chance that interested people will find it.

Signed-off-by: Petr Baudis <pasky@suse.cz>
---
 Documentation/git-read-tree.txt |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-read-tree.txt b/Documentation/git-read-tree.txt
index 7db5fb5..ff17bad 100644
--- a/Documentation/git-read-tree.txt
+++ b/Documentation/git-read-tree.txt
@@ -55,6 +55,12 @@ merge, a single tree merge if only 1 tre
 fast-forward merge with 2 trees, or a 3-way merge if 3 trees are
 provided.
 
+The detailed listing of the precise automatic resolution rules
+git-read-tree follows can be found in 'technical/trivial-merge.txt'.
+It is in part redundant with what you will find below since the
+fellow documenters cannot decide which of the descriptions is more
+confusing and remove the other one.
+
 
 Single Tree Merge
 ~~~~~~~~~~~~~~~~~
Next: Petr Baudis
Message 1 of 3 in “Reference technical/trivial-merge.txt in git-read-tree documentation”
  1. Reference technical/trivial-merge.txt in git-read-tree documentationPetr Baudis, Nov 11, 2005
  2. Petr BaudisNov 27, 2005
  3. Junio C HamanoNov 27, 2005

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.