already fixed
This commit is contained in:
parent
653462b9da
commit
e2ac9cf521
3 changed files with 31 additions and 1 deletions
|
@ -6,4 +6,5 @@ Thanks in advance for considering
|
|||
|
||||
[[!meta author=yoh]]
|
||||
[[!tag projects/datalad]]
|
||||
[[!tag confirmed]]
|
||||
|
||||
> [[done]]
|
||||
|
|
|
@ -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.
|
||||
"""]]
|
|
@ -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.
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue