From 0127e5f4e420242ad05d657428e5d22bff27ffd6 Mon Sep 17 00:00:00 2001
From: tomdhunt <tomdhunt@web>
Date: Mon, 7 Mar 2022 18:27:38 +0000
Subject: [PATCH] Added a comment

---
 ...comment_7_d52b1ab7d6a186919b3edfd51347e161._comment | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 doc/todo/git_smudge_clean_interface_suboptiomal/comment_7_d52b1ab7d6a186919b3edfd51347e161._comment

diff --git a/doc/todo/git_smudge_clean_interface_suboptiomal/comment_7_d52b1ab7d6a186919b3edfd51347e161._comment b/doc/todo/git_smudge_clean_interface_suboptiomal/comment_7_d52b1ab7d6a186919b3edfd51347e161._comment
new file mode 100644
index 0000000000..6bec8cff7d
--- /dev/null
+++ b/doc/todo/git_smudge_clean_interface_suboptiomal/comment_7_d52b1ab7d6a186919b3edfd51347e161._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="tomdhunt"
+ avatar="http://cdn.libravatar.org/avatar/02694633d0fb05bb89f025cf779218a3"
+ subject="comment 7"
+ date="2022-03-07T18:27:38Z"
+ content="""
+If you're dealing with a repository where you never intend to use unlocked files at all, does it work to just disable the smudge filter entirely?
+
+I'm currently running into the speed issues on `git add`, but I don't have any use for unlocked files in this particular use case, so I'd be happy just to turn off that whole step.
+"""]]