Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Added a comment: git remote | 2016-03-24 | |
| | |||
* | S3: Allow configuring with requeststyle=path to use path-style bucket access ↵ | 2016-02-09 | |
| | | | | | | instead of the default DNS-style access. untested | ||
* | Added a comment: attaching a torrent file to a downloaded and annexed directory | 2016-01-19 | |
| | |||
* | comment | 2015-12-10 | |
| | |||
* | response | 2015-12-10 | |
| | |||
* | Added a comment | 2015-12-09 | |
| | |||
* | Added a comment: anyone saw/worked on backend for watchdox service? (not ↵ | 2015-12-08 | |
| | | | | free one but needed :-/) | ||
* | Added a comment: How to view configuration of special remotes? | 2015-12-08 | |
| | |||
* | Added a comment: git-annex-remote-b2 | 2015-12-04 | |
| | |||
* | comment | 2015-11-30 | |
| | |||
* | removed | 2015-11-26 | |
| | |||
* | Added a comment: location of Mapping of file to tahoe uri? | 2015-11-26 | |
| | |||
* | Added a comment: location of Mapping of file to tahoe uri? | 2015-11-26 | |
| | |||
* | Added a comment: git-annex-remote-ipfs | 2015-11-19 | |
| | |||
* | remove badly offtopic comment | 2015-11-18 | |
| | |||
* | improve error message when special remote program cannot be run | 2015-11-18 | |
| | |||
* | Added a comment: Finding IPFS hash | 2015-11-18 | |
| | |||
* | Added a comment: Thanks | 2015-11-16 | |
| | |||
* | Added a comment: obnam | 2015-11-12 | |
| | |||
* | response | 2015-11-10 | |
| | |||
* | Added a comment: location of Mapping of file to tahoe uri? | 2015-11-06 | |
| | |||
* | removed | 2015-11-06 | |
| | |||
* | Added a comment: location of Mapping of file to tahoe uri? | 2015-11-06 | |
| | |||
* | removed | 2015-11-06 | |
| | |||
* | Added a comment: location of Mapping of file to tahoe uri? | 2015-11-06 | |
| | |||
* | Added a comment: backblaze support | 2015-11-04 | |
| | |||
* | Fix failure to build with aws-0.13.0 and finish nearline support. | 2015-11-02 | |
| | | | | | | * Fix failure to build with aws-0.13.0. * When built with aws-0.13.0, the S3 special remote can be used to create google nearline buckets, by setting storageclass=NEARLINE. | ||
* | enableremote: List uuids and descriptions of remotes that can be enabled, ↵ | 2015-10-26 | |
| | | | | and accept either the uuid or the description in leu if the name. | ||
* | Added a comment: Replicating my key for encrypted special remotes | 2015-10-25 | |
| | |||
* | response | 2015-10-19 | |
| | |||
* | Added a comment: Replicating my key for encrypted special remotes | 2015-10-17 | |
| | |||
* | response | 2015-10-12 | |
| | |||
* | Added a comment: Sharing S3 bucket between repos | 2015-10-09 | |
| | |||
* | S3 storage classes expansion | 2015-09-17 | |
| | | | | | | | | | | Added support for storageclass=STANDARD_IA to use Amazon's new Infrequently Accessed storage. Also allows using storageclass=NEARLINE to use Google's NearLine storage. The necessary changes to aws to support this are in https://github.com/aristidb/aws/pull/176 | ||
* | Added a comment: re: UnicodeDecodeError | 2015-08-26 | |
| | |||
* | Added a comment: Glacier-cli works, thanks, some encode / decode error now... | 2015-08-26 | |
| | |||
* | response | 2015-08-19 | |
| | |||
* | response | 2015-08-19 | |
| | |||
* | Added a comment: Not sure what is wrong... looks like `glacier` might be ↵ | 2015-08-18 | |
| | | | | called wrongly. | ||
* | Added a comment: buprepo doesn't work properly | 2015-08-17 | |
| | |||
* | response | 2015-08-14 | |
| | |||
* | Added a comment: Integrating Tahoe and Git annex using special remote | 2015-08-12 | |
| | |||
* | promote comment to todo | 2015-08-06 | |
| | |||
* | response | 2015-07-06 | |
| | |||
* | Added a comment: Limit max size of remote | 2015-06-17 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-06-05 | |
|\ | |||
* | | S3: Publically accessible buckets can be used without creds. | 2015-06-05 | |
| | | |||
* | | public=yes config to send AclPublicRead | 2015-06-05 | |
| | | | | | | | | | | | | | | | | | | | | | | In my tests, this has to be set when uploading a file to the bucket and then the file can be accessed using the bucketname.s3.amazonaws.com url. Setting it when creating the bucket didn't seem to make the whole bucket public, or allow accessing files stored in it. But I have gone ahead and also sent it when creating the bucket just in case that is needed in some case. | ||
| * | Added a comment: Tahoe-LAFS helper: multiple FURLs for the same grid | 2015-06-05 | |
|/ | |||
* | comment | 2015-06-02 | |
| |