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

update

Browse source
This commit is contained in:
Joey Hess 2018-08-31 12:23:04 -04:00
parent 6b75b9c448
commit 9d78a4387f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 2 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

7
doc/todo/versioning_in_export_remotes.mdwn
View file

@ -57,14 +57,11 @@ configured. done
Use version IDs when retrieving keys and for checkpresent. done Use version IDs when retrieving keys and for checkpresent. done
TODO testing When bucket is public, use version ID to generate public url.
And, support git-annex operations on public url to versioned content.
## other considerations ## other considerations
Can public urls be generated using version IDs? The url has
"?versionId=" appended, but all the examples I've seen include S3
authorization headers.
If the user enables versioning in git-annex but forgets to enable it If the user enables versioning in git-annex but forgets to enable it
in the bucket (or later suspends versioning in the bucket), it's no in the bucket (or later suspends versioning in the bucket), it's no
big problem; old files will not be retained and git-annex will notice big problem; old files will not be retained and git-annex will notice