From: Ben Peart <benpe...@microsoft.com>
When git reset is run with the --quiet flag, don't bother finding any
additional unstaged changes as they won't be output anyway. This speeds up
the git reset command by avoiding having to lstat() every file looking for
changes that aren't going to be reported anyway.
The savings can be significant. In a repo with 200K files "git reset"
drops from 7.16 seconds to 0.32 seconds for a savings of 96%.
Signed-off-by: Ben Peart <benpe...@microsoft.com>
---
Documentation/git-reset.txt | 4 +++-
builtin/reset.c | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-reset.txt b/Documentation/git-reset.txt
index 1d697d9962..8610309b55 100644
--- a/Documentation/git-reset.txt
+++ b/Documentation/git-reset.txt
@@ -95,7 +95,9 @@ OPTIONS
-q::
--quiet::
- Be quiet, only report errors.
+ Be quiet, only report errors. Can optimize the performance of reset
+ by avoiding scaning all files in the repo looking for additional
+ unstaged changes.
EXAMPLES
diff --git a/builtin/reset.c b/builtin/reset.c
index 11cd0dcb8c..0822798616 100644
--- a/builtin/reset.c
+++ b/builtin/reset.c
@@ -376,7 +376,7 @@ int cmd_reset(int argc, const char **argv, const char
*prefix)
if (read_from_tree(&pathspec, &oid, intent_to_add))
return 1;
if (get_git_work_tree())
- refresh_index(&the_index, flags, NULL, NULL,
+ refresh_index(&the_index, flags, quiet ?
&pathspec : NULL, NULL,
_("Unstaged changes after
reset:"));
} else {
int err = reset_index(&oid, reset_type, quiet);
--
2.18.0.windows.1
