This commit is contained in:
Joey Hess 2020-05-11 12:49:50 -04:00
parent 0e2e8df8bf
commit 568c2b58c2
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 38 additions and 0 deletions

View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2020-05-11T16:31:58Z"
content="""
I think it's quite likely that most people consider files in dotdirs to be
dotfiles, most of the time. (.git/index is clearly not a dotfile,
.git/config probably is) The exact semantics of it are vague enough that
it's probably better to not consider them when it comes to this bug report.
The actual bug is not about whether .foo/bar is a dotfile, but about
inconsistent behavior adding it.
Avoiding treating them as dotfiles, even if they're broadly understood as
such would resolve the inconsistency.
Otoh, the inconsistency only arises when run inside a dot directory,
which is probably a fairly rare thing to do.
"""]]

View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2020-05-11T16:40:46Z"
content="""
I'm also reluctant to start another behavior change in this area, there has
been more than enough drama around dotfile handling recently.
At least the behavior change would only result in small files that users
want to store in git being annexed, rather than large files being
unexpectedly put in git.
It would also be possible for users to get back the current behavior if
desired by configuring annex.dotfiles and annex.largefiles.
Also as far as the priority of this goes, I think that the number of
dotdirs that contain files that get version controlled at all is probably
quite small, excluding version controlling of HOME.
"""]]