Merge branch 'master' of ssh://git-annex.branchable.com

This commit is contained in:
Joey Hess 2016-09-26 16:49:21 -04:00
commit f3b84f4603
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
7 changed files with 208 additions and 0 deletions

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4"
subject="+may be "byte-target" field? ;)"
date="2016-09-24T02:43:21Z"
content="""
THANK YOU for implementing this feature -- we will make use of it soon.
But so we don't do reverse estimation from \"byte-progress\" and \"percent-progress\", and didn't have to get it from a key (which might not have it e.g. in case of URL relaxed backend) -- could you just include in each record the \"byte-target\" (if known) or something like that? ;) thanks in advance!
"""]]

View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="erics"
subject="comment 4"
date="2016-09-25T00:33:56Z"
content="""
> And there is a complication with running [`git annex copy --from --to`] at the same time as eg `git annex get` of the same file. It would be surprising for get to succeed (because copy has already temporarily downloaded the file) and then have the file later get dropped.
A solution to this subproblem would transparently fall out of a facility for [logically dropping files](http://git-annex.branchable.com/todo/wishlist__58_____96__git_annex_drop_--relaxed__96__/#comment-9672d46a18a381971dd818cde6efbc33), which was briefly talked about a long time ago. Just mark the file as *logically dropped*. If the user `git annex get`s it while the copy-out is in progress, its status will change to \"present\", so *copy* will know not to physically delete it.
(Of course there are race conditions involved, but I presume/hope that they're no worse than git-annex already has to deal with.)
"""]]