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

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

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

15
doc/tips/unlocked_files/comment_15_15a0dae4179d34420584ca532c1a2d51._comment
View file

@ -1,15 +0,0 @@
[[!comment format=mdwn
username="ginquistador@86f226616ead98d2733e249429918f241f928064"
nickname="ginquistador"
avatar="http://cdn.libravatar.org/avatar/f0ef7d68c0ff5d4948a9b0d282987195"
subject="Disappointed with `git add`"
date="2019-09-03T07:30:28Z"
content="""
I first have to say, I have been following and using git annex for ages (5+ years at least), and is my trusted source for all my data. However, for the first time in all these years, I'm seeing a decision that I do not agree with or understand.
Specifically, using `git add .` to add a file to git annex as the default pattern just seems a fundamentally wrong design to me (at least for my usage pattern). I want to be able to use git normally, and have git-annex only get involved when I explicitly request it to, and not for all files. AFAIK, git-lfs does do it right. I understand [annex.largefiles: configuring mixed content repositories](http://git-annex.branchable.com/tips/largefiles/) can be configured to get the behavior I want. However, the default behavior should add it to vanilla git, and any other desired behavior can be obtained by the user via annex attributes, or extra command line flags to `git annex add`
Knowing Joey, I assume there's a strong rationale as always, and would love to hear it, but I would still like to STRONGLY REQUEST changing the default behavior.
"""]]

8
doc/tips/unlocked_files/comment_16_d2ffb9afabc0109ac2da87fafc83006c._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 16"""
date="2019-09-16T17:36:06Z"
content="""
@ginquistador it may or may not have been the best decision, but this tip
is not a good place to discuss it. A bug would be a good place.
"""]]

7
doc/tips/unlocked_files/comment_17_d67bdea05b180858ccbcfbdb05dc5202._comment
View file

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