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

[PATCH 09/11] Document git read-tree --trivial

From
Jakub Narebski <jnareb@gmail.com>
Date
Jun 16, 2007, 19:03 UTC
Message-ID
<1182020635187-git-send-email-jnareb@gmail.com>
In-Reply-To
<11820206272990-git-send-email-jnareb@gmail.com>
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
 Documentation/git-read-tree.txt |    8 +++++++-
 builtin-read-tree.c             |    2 +-
 2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-read-tree.txt b/Documentation/git-read-tree.txt
index 84184d6..74c5478 100644
--- a/Documentation/git-read-tree.txt
+++ b/Documentation/git-read-tree.txt
@@ -8,7 +8,7 @@ git-read-tree - Reads tree information into the index
 
 SYNOPSIS
 --------
-'git-read-tree' (<tree-ish> | [[-m [--aggressive] | --reset | --prefix=<prefix>] [-u | -i]] [--exclude-per-directory=<gitignore>] [--index-output=<file>] <tree-ish1> [<tree-ish2> [<tree-ish3>]])
+'git-read-tree' (<tree-ish> | [[-m [--trivial] [--aggressive] | --reset | --prefix=<prefix>] [-u | -i]] [--exclude-per-directory=<gitignore>] [--index-output=<file>] <tree-ish1> [<tree-ish2> [<tree-ish3>]])
 
 
 DESCRIPTION
@@ -50,6 +50,12 @@ OPTIONS
 	trees that are not directly related to the current
 	working tree status into a temporary index file.
 
+--trivial::
+	Restrict three-way merge by `git-read-tree` to happen
+	only if there is no file-level merging required, instead
+	of resolving merge for trivial cases and leaving
+	conflicting files unresolved in the index.
+
 --aggressive::
 	Usually a three-way merge by `git-read-tree` resolves
 	the merge for really trivial cases and leaves other
diff --git a/builtin-read-tree.c b/builtin-read-tree.c
index 316fb0f..41f8110 100644
--- a/builtin-read-tree.c
+++ b/builtin-read-tree.c
@@ -84,7 +84,7 @@ static void prime_cache_tree(void)
 
 }
 
-static const char read_tree_usage[] = "git-read-tree (<sha> | [[-m [--aggressive] | --reset | --prefix=<prefix>] [-u | -i]] [--exclude-per-directory=<gitignore>] [--index-output=<file>] <sha1> [<sha2> [<sha3>]])";
+static const char read_tree_usage[] = "git-read-tree (<sha> | [[-m [--trivial] [--aggressive] | --reset | --prefix=<prefix>] [-u | -i]] [--exclude-per-directory=<gitignore>] [--index-output=<file>] <sha1> [<sha2> [<sha3>]])";
 
 static struct lock_file lock_file;
 
-- 
1.5.2
Previous: Jakub NarebskiNext: Jakub Narebski
Message 10 of 14 in “Document missing options”
  1. 00/11 Document missing optionsJakub Narebski, Jun 16, 2007
  2. 01/11 Use tabs for indenting definition list for options in git-log.txtJakub Narebski, Jun 16, 2007
  3. 02/11 Document git log --full-diffJakub Narebski, Jun 16, 2007
  4. 03/11 Document git log --abbrev-commit, as a kind of pretty optionJakub Narebski, Jun 16, 2007
  5. 04/11 Document that '--message=<msg>' is long version of '-m <msg>'Jakub Narebski, Jun 16, 2007
  6. 05/11 Document that '--no-checkout' is long version of '-n' option of git-cloneJakub Narebski, Jun 16, 2007
  7. 06/11 Document git rev-list --timestampJakub Narebski, Jun 16, 2007
  8. 07/11 Document git rev-list --full-historyJakub Narebski, Jun 16, 2007
  9. 08/11 Document git rev-parse --is-inside-git-dirJakub Narebski, Jun 16, 2007
  10. 09/11 Document git read-tree --trivialJakub Narebski, Jun 16, 2007
  11. 10/11 Document git reflog --stale-fixJakub Narebski, Jun 16, 2007
  12. 11/11 Document git commit --untracked-files and --verboseJakub Narebski, Jun 16, 2007
  13. Junio C HamanoJun 16, 2007
  14. Jakub NarebskiJun 16, 2007

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.