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

Added a comment

Browse source
This commit is contained in:
yarikoptic 2025-06-22 03:53:19 +00:00 • committed by admin
parent de905c7f7b
commit 6c95fd004a
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_8_52510b89aa6a287493f2f77c07b8a682._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="yarikoptic"
avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
subject="comment 8"
date="2025-06-22T03:53:19Z"
content="""
I did spend some time now trying to figure FTW and why git-annex (version from end of last year) says \"non-large file; adding content to git repository\" whenever `check-attr` insists that `largefile` should apply to my huge `.dandi/assets.json`. Only trying newer git-annex I think I got the reason which it finally announced as \"dotfile; adding content to git repository\" and I was able to recover this discussion!
Re
> But, .config/ seems to me to perfectly match what dotfiles are, which is files that are configuration that are named with a name starting with a dot in order to keep them from cluttering up ls.
As far as I know, having leading dot just a convention for **hidden** and not config, and even not neccessarily text files.
Even though, `dotfile` files (not folders) are most of the time are text files, I would not generalize that to dot-folders:
content of `.cache/` or `.venv/` (created by `uv`) etc are unlikely to be text files to even start with. Those folder names start with dot to signal \"hidden\" not \"text\" or \"small\".
That is why I retain that it remains confusing and inconsistent to have any special treatment and need for extra configuration (`git annex config --set annex.dotfiles true`) for content of dot-folders. I appreciate that such change would likely change behavior but IMHO it might just be \"for the best\".
"""]]