From 655235319be83f2096c84a02c2bbdce44016becf Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 28 Jun 2022 13:04:41 -0400 Subject: [PATCH] comment --- ..._2ce9c3c35ea5c4033bfa42e2f3365a64._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/todo/add_--json-progress_to_fsck_--json/comment_2_2ce9c3c35ea5c4033bfa42e2f3365a64._comment diff --git a/doc/todo/add_--json-progress_to_fsck_--json/comment_2_2ce9c3c35ea5c4033bfa42e2f3365a64._comment b/doc/todo/add_--json-progress_to_fsck_--json/comment_2_2ce9c3c35ea5c4033bfa42e2f3365a64._comment new file mode 100644 index 0000000000..7fb6967d69 --- /dev/null +++ b/doc/todo/add_--json-progress_to_fsck_--json/comment_2_2ce9c3c35ea5c4033bfa42e2f3365a64._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2022-06-28T17:00:33Z" + content=""" +It seems problimatic to have json progress for both downloading the file +and for checksumming it. I don't know how that json would look. + +In the meantime, though, git-annex has changed to checksum files while they +are being downloaded from most remotes, and when it can do that, fsck +--from avoids the separate checksumming step. + +While some special remotes do not support that, it's a very limited list: +only bittorrent on linux, and adb, external, gcrypt, hook, and rsync on +other OSs. + +This makes me think that complicating the json output to display two +different kinds of progress is probably not worth the complication. +"""]]