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

Added a comment: A new user chiming in

Browse source
This commit is contained in:
strmd 2019-10-14 18:23:59 +00:00 • committed by admin
parent 25e78d5f22
commit d671481ed7
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/forum/lets_discuss_git_add_behavior/comment_16_7ba4c08b3ab5753907e87781e15ba4e4._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="strmd"
avatar="http://cdn.libravatar.org/avatar/035707b9756129bbdea6b36a7f7b38d3"
subject="A new user chiming in"
date="2019-10-14T18:23:59Z"
content="""
I, too, am bewildered by how this major, breaking change was implemented and communicated so casually. Having basically been drawn in by the default v5 workflow and just barely finished migrating all of my archives/data sets and many of my current projects, I was initially convinced I must have not understood something right. But here we are, and at least I'm glad I'm not alone.
To a certain extent, I get that git-annex users are expected to be pretty savvy, but the auto-upgrade caught me completely by suprise. I'm on a Mac and ran `brew upgrade ` as part of everyday maintenance, made some changes in my repo, synced it to a remote and to my complete surprise was the repo now behaving the exact opposite way as the day before, i.e. `git add` annexed the file.
I am super happy about git-annex and your work on it Joey, but this has been a scary experience for me. And I'd very much like the default v5 workflow back.
"""]]