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

already fixed

Browse source
This commit is contained in:
Joey Hess 2020-01-30 12:40:39 -04:00
parent 653462b9da
commit e2ac9cf521
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 31 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls.mdwn
View file

@ -6,4 +6,5 @@ Thanks in advance for considering
[[!meta author=yoh]]
[[!tag projects/datalad]]
[[!tag confirmed]]
> [[done]]

17
doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_4_ceb543ebac42bf7a5f1571ff3f4ef977._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2020-01-30T16:23:55Z"
content="""
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.
"""]]

12
doc/todo/config_setting_to_force_--progress_reporting_for_some_git_calls/comment_5_ec99ba117fac299fc361a32de4ff29a5._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2020-01-30T16:38:30Z"
content="""
Heh, looking at the code, [[!commit
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.
"""]]