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

[PATCH v3 03/11] update-index: add --test-untracked-cache

From
Christian Couder <christian.couder@gmail.com>
Date
Dec 23, 2015, 21:03 UTC
Message-ID
<1450904639-25592-4-git-send-email-chriscool@tuxfamily.org>
In-Reply-To
<1450904639-25592-1-git-send-email-chriscool@tuxfamily.org>

It is nice to just be able to test if untracked cache is supported without enabling it.

Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 Documentation/git-update-index.txt | 9 ++++++++-
 builtin/update-index.c             | 5 +++++
 2 files changed, 13 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index f4e5a85..a0ee0c9 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -18,7 +18,7 @@ SYNOPSIS
 	     [--[no-]skip-worktree]
 	     [--ignore-submodules]
 	     [--[no-]split-index]
-	     [--[no-|force-]untracked-cache]
+	     [--[no-|test-|force-]untracked-cache]
 	     [--really-refresh] [--unresolve] [--again | -g]
 	     [--info-only] [--index-info]
 	     [-z] [--stdin] [--index-version <n>]
@@ -180,6 +180,13 @@ may not support it yet.
 	system must change `st_mtime` field of a directory if files
 	are added or deleted in that directory.
 
+--test-untracked-cache::
+	Only perform tests on the working directory to make sure
+	untracked cache can be used. You have to manually enable
+	untracked cache using `--force-untracked-cache` (or
+	`--untracked-cache` but this will run the tests again)
+	afterwards if you really want to use it.
+
 --force-untracked-cache::
 	For safety, `--untracked-cache` performs tests on the working
 	directory to make sure untracked cache can be used. These
diff --git a/builtin/update-index.c b/builtin/update-index.c
index 1e546a3..62222dd 100644
--- a/builtin/update-index.c
+++ b/builtin/update-index.c
@@ -40,6 +40,7 @@ enum uc_mode {
 	UC_UNSPECIFIED = -1,
 	UC_DISABLE = 0,
 	UC_ENABLE,
+	UC_TEST,
 	UC_FORCE
 };
 
@@ -1004,6 +1005,8 @@ int cmd_update_index(int argc, const char **argv, const char *prefix)
 			N_("enable or disable split index")),
 		OPT_BOOL(0, "untracked-cache", &untracked_cache,
 			N_("enable/disable untracked cache")),
+		OPT_SET_INT(0, "test-untracked-cache", &untracked_cache,
+			    N_("test if the filesystem supports untracked cache"), UC_TEST),
 		OPT_SET_INT(0, "force-untracked-cache", &untracked_cache,
 			    N_("enable untracked cache without testing the filesystem"), UC_FORCE),
 		OPT_END()
@@ -1119,6 +1122,8 @@ int cmd_update_index(int argc, const char **argv, const char *prefix)
 			setup_work_tree();
 			if (!test_if_untracked_cache_is_supported())
 				return 1;
+			if (untracked_cache == UC_TEST)
+				return 0;
 		}
 		if (!the_index.untracked) {
 			uc = xcalloc(1, sizeof(*uc));
-- 
2.7.0.rc2.11.g68ccdd4
Previous: Christian CouderNext: Christian Couder
Message 4 of 18 in “Untracked cache improvements”
  1. 00/11 Untracked cache improvementsChristian Couder, Dec 23, 2015
  2. 01/11 dir: free untracked cache when removing itChristian Couder, Dec 23, 2015
  3. 02/11 update-index: use enum for untracked cache optionsChristian Couder, Dec 23, 2015
  4. 03/11 update-index: add --test-untracked-cacheChristian Couder, Dec 23, 2015
  5. 04/11 update-index: add untracked cache notificationsChristian Couder, Dec 23, 2015
  6. Duy NguyenDec 24, 2015
  7. Christian CouderDec 24, 2015
  8. 05/11 update-index: move 'uc' var declarationChristian Couder, Dec 23, 2015
  9. 06/11 dir: add add_untracked_cache()Christian Couder, Dec 23, 2015
  10. 07/11 dir: add new_untracked_cache()Christian Couder, Dec 23, 2015
  11. Eric SunshineDec 23, 2015
  12. Christian CouderDec 24, 2015
  13. 08/11 dir: add remove_untracked_cache()Christian Couder, Dec 23, 2015
  14. 09/11 dir: simplify untracked cache "ident" fieldChristian Couder, Dec 23, 2015
  15. 10/11 config: add core.untrackedCacheChristian Couder, Dec 23, 2015
  16. Duy NguyenDec 24, 2015
  17. Christian CouderDec 24, 2015
  18. 11/11 t7063: add tests for core.untrackedCacheChristian Couder, Dec 23, 2015

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.