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

[PATCH] add --no-check option to git-write-tree

From
Bryan Larsen <bryan.larsen@gmail.com>
Date
Jul 8, 2005, 10:37 UTC
Message-ID
<42CE577C.1070404@gmail.com>
Add --no-check option to git-write-tree.
Signed-off-by: Bryan Larsen <bryan.larsen@gmail.com>
---
  Documentation/git-write-tree.txt |    6 ++++++
  write-tree.c                     |   14 +++++++++++++-
  2 files changed, 19 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-write-tree.txt 
b/Documentation/git-write-tree.txt
--- a/Documentation/git-write-tree.txt
+++ b/Documentation/git-write-tree.txt
@@ -10,6 +10,7 @@ git-write-tree - Creates a tree from the
  SYNOPSIS
  --------
  'git-write-tree'
+		[--no-check]

  DESCRIPTION
  -----------
@@ -23,6 +24,11 @@ In order to have that match what is actu
  now, you need to have done a "git-update-cache" phase before you did the
  "git-write-tree".

+OPTIONS
+-------
+--no-check::
+	Normally "git-write-tree" ensures that the objects referenced by the
+	directory exist in the object database.  This option disabled this check.



diff --git a/write-tree.c b/write-tree.c
--- a/write-tree.c
+++ b/write-tree.c
@@ -5,6 +5,8 @@
   */
  #include "cache.h"

+static int no_check = 0;
+
  static int check_valid_sha1(unsigned char *sha1)
  {
  	int ret;
@@ -61,7 +63,7 @@ static int write_tree(struct cache_entry
  			sha1 = subdir_sha1;
  		}

-		if (check_valid_sha1(sha1) < 0)
+		if (!no_check && check_valid_sha1(sha1) < 0)
  			exit(1);

  		entrylen = pathlen - baselen;
@@ -86,6 +88,16 @@ int main(int argc, char **argv)
  	int i, funny;
  	int entries = read_cache();
  	unsigned char sha1[20];
+	
+	if (argc==2) {
+		if (!strcmp(argv[1], "--no-check"))
+			no_check = 1;
+		else
+			die("unknown option %s", argv[1]);
+	}
+	
+	if (argc>2)
+		die("too many options");

  	if (entries < 0)
  		die("git-write-tree: error reading cache");



Next: Linus Torvalds
Message 1 of 2 in “add --no-check option to git-write-tree”
  1. add --no-check option to git-write-treeBryan Larsen, Jul 8, 2005
  2. Linus TorvaldsJul 8, 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.