diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-03-31 15:40:08 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-03-31 15:40:08 -0400 |
| commit | a76d1cda912ebdc31211ef92e1ddfef4b4295e41 (patch) | |
| tree | 1fc01c34a12b9d743251debf8a74c6dabc9ae49d /doc/bugs/check_for_curl_in_configure.hs.mdwn | |
| parent | a7680717f6600469c6920e22cc3dffac06993b1b (diff) | |
update
Diffstat (limited to 'doc/bugs/check_for_curl_in_configure.hs.mdwn')
| -rw-r--r-- | doc/bugs/check_for_curl_in_configure.hs.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/check_for_curl_in_configure.hs.mdwn b/doc/bugs/check_for_curl_in_configure.hs.mdwn index 2a5227491..a880392bf 100644 --- a/doc/bugs/check_for_curl_in_configure.hs.mdwn +++ b/doc/bugs/check_for_curl_in_configure.hs.mdwn @@ -53,6 +53,14 @@ index 772ba54..1a563e0 100644 >>> A S3 backend that could upload files to S3 in addition to downloading >>> them, for example, would be handy. --[[Joey]] +>>>> So, rather than use backends to do this, it instead made more sense +>>>> to make them [[special_remotes]]. The URL backend remains a bit +>>>> of a special case, and a bittorrent backend that downloaded a file +>>>> from a bittorrent url would still be a good use of backend, but for +>>>> storing files in external data stores like S3, making it a remote +>>>> makes better sense. I think I can close this bug now, [[done]] +>>>> --[[Joey]] + also in Backend/URL.hs is it worth making a minor change to the way curl is called (I'm not sure if the following is correct or not) > It's correct, typewise, but I don't see any real reason to bother |