From e6692b66f105ad3dd2a9d8a49eca57d0c7220eca Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 11 Dec 2020 15:49:39 -0400 Subject: [PATCH] remove I need to think about this some more, not clear if it's a todo item specific to stalldetection at all. Remotes with this behavior also show no progress when run with -J. And some other remotes don't update any progress meters at all, eg adb is that way and so are hook remotes and of course external remotes don't have to send progress info. --- ...ldetection_does_not_work_for_rsync_and_gcrypt.mdwn | 11 ----------- 1 file changed, 11 deletions(-) delete mode 100644 doc/todo/stalldetection_does_not_work_for_rsync_and_gcrypt.mdwn diff --git a/doc/todo/stalldetection_does_not_work_for_rsync_and_gcrypt.mdwn b/doc/todo/stalldetection_does_not_work_for_rsync_and_gcrypt.mdwn deleted file mode 100644 index 56e6acfb12..0000000000 --- a/doc/todo/stalldetection_does_not_work_for_rsync_and_gcrypt.mdwn +++ /dev/null @@ -1,11 +0,0 @@ -When annex.stalldetection is set, rsync and gcrypt -special remotes do not display any progress. Also, the stall detection -cannot detect stalls, because that needs progress information to do. - -These remotes have `displayProgress = False`, and seem to be the only -affected ones. - -It seems like it would be a good idea to make these remotes capture the -output of the program they run, and convert it to a progress meter. - -(Also, these don't have progress output with -J either..) -- 2.30.2