From 4f8b9f50f8e1439ff1d36cdef4af9ba1faa54c24 Mon Sep 17 00:00:00 2001 From: pat Date: Sat, 9 Jul 2022 00:40:23 +0000 Subject: [PATCH] Added a comment --- ...comment_1_a32e4d4255a1afcfd05c374d0fffccab._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/git_status_is_slow_twice__44___then_fast/comment_1_a32e4d4255a1afcfd05c374d0fffccab._comment diff --git a/doc/forum/git_status_is_slow_twice__44___then_fast/comment_1_a32e4d4255a1afcfd05c374d0fffccab._comment b/doc/forum/git_status_is_slow_twice__44___then_fast/comment_1_a32e4d4255a1afcfd05c374d0fffccab._comment new file mode 100644 index 0000000000..810e80a7e6 --- /dev/null +++ b/doc/forum/git_status_is_slow_twice__44___then_fast/comment_1_a32e4d4255a1afcfd05c374d0fffccab._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="pat" + avatar="http://cdn.libravatar.org/avatar/6b552550673a6a6df3b33364076f8ea8" + subject="comment 1" + date="2022-07-09T00:40:23Z" + content=""" +Alright I did some reading and experimenting, and it turns out it's the unlocked files. When I use locked files by defaults, git status is as fast as it usually is. I don't fully understand it, but it seems that something about smudging is slow. + +Anyway, I can use locked files for most of my stuff, and unlocked files for only active projects. +"""]] -- 2.30.2