Ref: all heated discussions around https://github.com/datalad/datalad/issues/2844
The main point is -- git annex init --version=6, while running on a crippled system might need some time to accomplish the mission of unlocking a big number of files, which leads to Checking out progress update spit out by git. BUT if someone (us) swallows stderr, git does not produce any progress output unless that command (checkout, pull, fetch, etc...) provides explicit --progress flag. According to IRC there is no config setting to trigger that behavior in git. Could may be git annex get a config setting alike force-git-progress which would add --progress to any relevant git call whenever git is ran without stderr being swallowed by annex?
Thanks in advance for considering
Hrm, git checkout does not have a --progress flag that I can see. Perhaps they were thinking about git clone, which does have a progress, but the repo is already cloned at this point.
hm...
Ah, I see, I was searching for "--progress".
I suppose what would make sense is to add the same option to the git-annex commands that can do a git checkout: init, adjust, sync, view, vpop, vadd, vcycle.
Occurs to me that any git-annex command could result in an automatic init, and since v7 is default, will enter an adjusted branch when on a crippled filesystem.
I don't think it makes sense to add --progress to every single git-annex command.
I suppose, if your code always runs git-annex init after clone, then it would be good enough to have git-annex init be the only thing that supports --progress. If something else needs it (maybe the view commands), we can treat that separately.
Heh, looking at the code, 24838547e2475b37d7e910361f9b6e087a1a0648 in 2018 made --progress be unconditionally passed when entering an adjusted branch.
That was done for unrelated reasons, but I don't think there's anything more to do on this now.