diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw <Carl@web> | 2015-10-02 09:25:02 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-10-02 09:25:02 +0000 |
| commit | 58c82c3bf239b9f9a59fbc00ad1c81a2f7f9b52c (patch) | |
| tree | d332fceaff32f575ce30d89d84e0762051fa669a | |
| parent | e4657080d15d664a1128eb5e6680a0a177c1851f (diff) | |
| -rw-r--r-- | doc/forum/external_special_remote_protocol_and_threads.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/external_special_remote_protocol_and_threads.mdwn b/doc/forum/external_special_remote_protocol_and_threads.mdwn new file mode 100644 index 000000000..93b370d4e --- /dev/null +++ b/doc/forum/external_special_remote_protocol_and_threads.mdwn @@ -0,0 +1,3 @@ +As the sync command just got a -J option I have started to use threads to transfer new files to multiple remotes in parallel. A question that arises is if I still can assume that only one instance of the special remote will be started. I tend to store quite some state in the special remote program that I use to connect to a cloud server, and running two instances in parallel might run in to all sorts of fun behavior. + +That said, I am of course aware that if I run multiple git annex commands I would run into these problems. |