From: asakurareiko@f3d908c71c009580228b264f63f21c7274df7476 <asakurareiko@web>
Date: Thu, 21 Oct 2021 17:17:42 +0000 (+0000)
Subject: (no commit message)
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~79^2~101^2~12
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=f9e09277c5a587fac93a2405290aa7ad76d1079f;p=git-annex.git

---

diff --git a/doc/bugs/git_commit_smudges_unncessarily.mdwn b/doc/bugs/git_commit_smudges_unncessarily.mdwn
new file mode 100644
index 0000000000..b0aae6b491
--- /dev/null
+++ b/doc/bugs/git_commit_smudges_unncessarily.mdwn
@@ -0,0 +1,20 @@
+### Please describe the problem.
+
+git commit smudges unlocked files in the index when they were already smudged with git status.
+
+### What steps will reproduce the problem?
+
+```
+for i in {1..200}; do echo $i > $i; done
+git init; git annex init; git config annex.thin true; git config annex.crippledfilesystem true; git config annex.addunlocked true; git annex add .; git status; time git commit -m .
+```
+
+git commit should take less than a second but takes several seconds to smudge the files in the index.
+
+### What version of git-annex are you using? On what operating system?
+
+Through bisection, the problem was found to be introduced in [[!commit 428c91606b434512d1986622e751c795edf4df44]]. Problem occurs both in Linux and WSL1.
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+
+git-annex has worked wonderfully for managing my files across different machines and cloud storage services.