mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

status update

Browse source 
I was wrong about S3 supporting tailVerify.
This commit is contained in:
Joey Hess 2021-08-16 15:15:32 -04:00
parent aac0654ff4
commit ec82299730
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 18 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
CHANGELOG
View file

@ -11,7 +11,7 @@ git-annex (8.20210804) UNRELEASED; urgency=medium
* Special remotes now checksum content while it is being retrieved,
instead of in a separate pass at the end. This is supported for all
special remotes on Linux (except for web and bittorrent), and for a
few on other OSs (S3, bup, ddar, gcrypt).
few on other OSs (bup, ddar, gcrypt, glacier).
-- Joey Hess <id@joeyh.name> Tue, 03 Aug 2021 12:22:45 -0400

17
doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_16_fbbcf1d8b35078274cfe322cea6de21c._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 16"""
date="2021-08-16T19:08:29Z"
content="""
The concurrency problem is fixed now.
As well as the web special remote, these do not do incremental hashing
still: directory, gitlfs, webdav, S3.
The ones that do are: external, adb, gcrypt, hook, rsync
The issue with directory etc is that they open the file
for write. This prevents tailVerify re-opening it for read, because the
haskell RTS actually does not allowing opening a file for read that it has
open for write.
"""]]