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 2011-03-31 15:40:08 -04:00
parent a7680717f6
commit a76d1cda91
2 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/Unfortunate_interaction_with_Calibre/comment_2_b8ae4bc589c787dacc08ab2ee5491d6e._comment
View file

@ -4,5 +4,5 @@
subject="comment 2"
date="2011-03-31T19:32:25Z"
content="""
One option would be to use the new [[sharebox_a_FUSE_filesystem_for_git-annex]], which would hide the immutable file details from Calibre, and proxy any changes it made through to git-annex as a series of `git annex unlock; modify; git-annex lock`
One option would be to use the new [[news/sharebox_a_FUSE_filesystem_for_git-annex]], which would hide the immutable file details from Calibre, and proxy any changes it made through to git-annex as a series of `git annex unlock; modify; git-annex lock`
"""]]

8
doc/bugs/check_for_curl_in_configure.hs.mdwn
View file

@ -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