documentation for making git add only annex when configured by annex.largefiles

Code change should be trvial, but not yet implemented. This
significantly complicated the task of documenting how git-annex works.

I'm not sure how useful the annex.gitaddtoannex confguration is after
this change; seems that if a user has an annex.largefiles they will want
it applied consistently. But the last thing I want to hear is more
complaining from users about git add doing something they don't want it
to.

There's a pretty high risk users who got used to the git add behavior
and don't have annex.largefiles configured will miss the NEWS and
complain bitterly about their suddenly bloated repositories. Oh well.

Removed outdated comments about the old behavior to avoid confusion.
I don't know if I've found all the places that griping spread to.
This commit is contained in:
Joey Hess 2019-10-24 13:50:44 -04:00
parent 64d4a35523
commit 31a5b58b2c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
14 changed files with 111 additions and 138 deletions

View file

@ -1,7 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 12"""
date="2019-09-16T18:43:02Z"
content="""
[[forum/lets_discuss_git_add_behavior]]
"""]]

View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="hoxu"
avatar="http://cdn.libravatar.org/avatar/95e33a0073f6c06477b3a202f0301dde"
subject="v6 & manual annexation"
date="2017-06-29T07:25:31Z"
content="""
With v6, is there any way to retain old usage of `git add` and `git annex add` to manually choose which files are kept under plain git and which annexed?
I'm aware of the `-c annex.largefiles=foo` parameter, but that's pretty cumbersome.
"""]]