diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_19_c1d6b7ae3b7cc0f7f0dc8d55cf629508._comment b/doc/forum/lets_discuss_git_add_behavior/comment_19_c1d6b7ae3b7cc0f7f0dc8d55cf629508._comment new file mode 100644 index 0000000000..30b97461d5 --- /dev/null +++ b/doc/forum/lets_discuss_git_add_behavior/comment_19_c1d6b7ae3b7cc0f7f0dc8d55cf629508._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="different handling of dotfiles" + date="2019-10-21T02:51:16Z" + content=""" +Related: [[bugs/dotfiles_handled_differently]] + +For most files, whether they get annexed is controlled by `annex.largefiles`. But dotfiles are configured to never be annexed regardless of `annex.largefiles`. This special-casing (in `.git/info/attributes`) is unexpected and confusing. It is probably a consequence of making `git add` annex files by default, but it's better to change that default than to have the special case. Also, `git-annex-add` seems to ignore the dotfiles, as in the bug report above. + +I thought of reverting to an earlier version of git-annex until these and other issues can get worked out, but realized I can't, since the repos got irreversibly auto-upgraded to v7... +"""]]