From 0f4531e9a7e1473e0e662d43233cd8420b77f099 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 23 Jun 2025 10:30:00 -0400 Subject: [PATCH] response --- ...9_022c07b37308d43a1afb1999d5379c99._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/add__58___inconsistently_treats_files_in_dotdirs_as_dotfiles/comment_9_022c07b37308d43a1afb1999d5379c99._comment diff --git a/doc/bugs/add__58___inconsistently_treats_files_in_dotdirs_as_dotfiles/comment_9_022c07b37308d43a1afb1999d5379c99._comment b/doc/bugs/add__58___inconsistently_treats_files_in_dotdirs_as_dotfiles/comment_9_022c07b37308d43a1afb1999d5379c99._comment new file mode 100644 index 0000000000..f4f5a87f52 --- /dev/null +++ b/doc/bugs/add__58___inconsistently_treats_files_in_dotdirs_as_dotfiles/comment_9_022c07b37308d43a1afb1999d5379c99._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 9""" + date="2025-06-23T14:20:44Z" + content=""" +(Note that this is a bug that has already been closed.) + +While yes, leading dot just means "hide it from ls", people *do* have a +legitimate complaint when `git-annex add` annexes .gitattributes or a file +like that. Since we don't have any other general semantic information about +config files besides leading dot, this seems to be to be the best that can +be done to avoid what would otherwise be a common complaint, and turn it +into an uncommon complaint. + +The only other good approach seems to be the git-lfs approach, of requiring +that the user configure explicitly which files they consider large, with eg +`git lfs track "*.iso"` +"""]]