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

fix commment

Browse source
This commit is contained in:
Joey Hess 2020-07-02 20:05:36 -04:00
parent 51aa291b20
commit 8fc9788363
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 20 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/import_tree_on_adjusted_unlocked_branch_issues/comment_2_7fc16d6ff0f1a61907bc34e8f8b71adc._comment
View file

@ -2,7 +2,7 @@
username="joey"
subject="""comment 2"""
date="2020-07-02T18:36:55Z"
content=""
content="""
There's a simple workaround, in fact. Make a git commit, any git commit.
An empty commit will do:

19
doc/todo/idea__58___external_special_remote___34__async__34___protocol_for_transfers/comment_5_ab2c969b5b561b75fec1d95c52598cb4._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2020-07-03T00:02:07Z"
content="""
> May be if async remotes were not "parallelizable" (i.e. only a single
> such remote would start even in the case of -J > 1) - it would simplify
> it?
I'm assuming only 1 that is used for transfers, others could be used for
other things.
> Isn't there some point in time when annex knows that it is done issuing all possible TRANSFER requests it knew to issue and could just send out "initiate TRANSFER" to those special remotes it knows are waiting for it?
Not really, it starts as many threads as it's allowed to as soon as it has
some files to work on, and as each thread finishes it starts a new one.
Only time it knows it's done is after it's checked the whole tree of files,
but that could be much much later.
"""]]