mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

response

Browse source
This commit is contained in:
Joey Hess 2025-06-23 10:30:00 -04:00
parent 7b88bc4970
commit 0f4531e9a7
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/add__58___inconsistently_treats_files_in_dotdirs_as_dotfiles/comment_9_022c07b37308d43a1afb1999d5379c99._comment Normal file
View file

@ -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"`
"""]]