aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/tor.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-12-08 19:56:02 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-12-08 19:56:02 -0400
commit1d9ba9d9459b44c306b7c4f261b84bad38185109 (patch)
tree5b46c5cd6450cf7ad9ef1f4e20ffe74135d0ef7b /doc/todo/tor.mdwn
parent691eeb92d9fc4ffc445750a279d125f272934897 (diff)
update progress logs in remotedaemon send/receive
Diffstat (limited to 'doc/todo/tor.mdwn')
-rw-r--r--doc/todo/tor.mdwn1
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/todo/tor.mdwn b/doc/todo/tor.mdwn
index 79822ab19..01fa2635a 100644
--- a/doc/todo/tor.mdwn
+++ b/doc/todo/tor.mdwn
@@ -8,7 +8,6 @@ Current todo list:
object is already in progress, the message about this is output by the
remotedaemon --debug, but not forwarded to the peer, which shows
"Connection reset by peer"
-* update progress logs in remotedaemon send/receive
* Think about locking some more. What happens if the connection to the peer
is dropped while we think we're locking content there from being dropped?