comment
This commit is contained in:
parent
53a4de4968
commit
655235319b
1 changed files with 19 additions and 0 deletions
|
@ -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.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue