ef3457196a
To get old behavior, add a .gitattributes containing: * annex.backend=WORM I feel that SHA256 is a better default for most people, as long as their systems are fast enough that checksumming their files isn't a problem. git-annex should default to preserving the integrity of data as well as git does. Checksum backends also work better with editing files via unlock/lock. I considered just using SHA1, but since that hash is believed to be somewhat near to being broken, and git-annex deals with large files which would be a perfect exploit medium, I decided to go to a SHA-2 hash. SHA512 is annoyingly long when displayed, and git-annex displays it in a few places (and notably it is shown in ls -l), so I picked the shorter hash. Considered SHA224 as it's even shorter, but feel it's a bit weird. I expect git-annex will use SHA-3 at some point in the future, but probably not soon! Note that systems without a sha256sum (or sha256) program will fall back to defaulting to SHA1. |
||
---|---|---|
.. | ||
bugs | ||
design | ||
download | ||
encryption | ||
forum | ||
install | ||
news | ||
special_remotes | ||
templates | ||
tips | ||
todo | ||
upgrades | ||
use_case | ||
users | ||
walkthrough | ||
backends.mdwn | ||
bare_repositories.mdwn | ||
bugs.mdwn | ||
comments.mdwn | ||
contact.mdwn | ||
copies.mdwn | ||
design.mdwn | ||
distributed_version_control.mdwn | ||
download.mdwn | ||
encryption.mdwn | ||
feeds.mdwn | ||
forum.mdwn | ||
future_proofing.mdwn | ||
git-annex-shell.mdwn | ||
git-annex.mdwn | ||
git-union-merge.mdwn | ||
GPL | ||
index.mdwn | ||
install.mdwn | ||
internals.mdwn | ||
location_tracking.mdwn | ||
logo.png | ||
logo_small.png | ||
news.mdwn | ||
not.mdwn | ||
repomap.png | ||
special_remotes.mdwn | ||
summary.mdwn | ||
tips.mdwn | ||
todo.mdwn | ||
transferring_data.mdwn | ||
trust.mdwn | ||
upgrades.mdwn | ||
users.mdwn | ||
walkthrough.mdwn |