interesting quote
This commit is contained in:
parent
63f70c44fd
commit
ea55609e54
2 changed files with 20 additions and 0 deletions
14
doc/design/assistant/blog/day_80__default_backend.mdwn
Normal file
14
doc/design/assistant/blog/day_80__default_backend.mdwn
Normal file
|
@ -0,0 +1,14 @@
|
|||
I've changed the default backend used by git-annex from SHA256 to SHA256E.
|
||||
Including the filename extension in the key is known to make repositories
|
||||
more usable on things like MP3 players, and I've recently learned it also
|
||||
avoids [[forum/Weird_behavior_with_OS_X_Finder_and_Preview.app]].
|
||||
|
||||
I thought about only changing the default in repositories set up by the
|
||||
assistant, but it seemed simpler to change the main default. The old
|
||||
backend is really only better if you might have multiple copies of files
|
||||
with the same content that have different extensions.
|
||||
|
||||
Fixed the socket leak in pairing that eluded me earlier.
|
||||
|
||||
I've made a new [[polls]] page, and posted a poll:
|
||||
[[polls/prioritizing_special_remotes]]
|
|
@ -17,3 +17,9 @@ vault becomes available, and the user could queue a list of commands to
|
|||
run, or files to transfer, at that point.
|
||||
|
||||
--[[Joey]]
|
||||
|
||||
-----
|
||||
|
||||
> In the coming months, Amazon S3 will introduce an option that will allow customers to seamlessly move data between Amazon S3 and Amazon Glacier based on data lifecycle policies.
|
||||
|
||||
-- <http://aws.amazon.com/glacier/faqs/#How_should_I_choose_between_Amazon_Glacier_and_Amazon_S3>
|
||||
|
|
Loading…
Reference in a new issue