summaryrefslogtreecommitdiff
path: root/doc/backends.mdwn
Commit message (Collapse)AuthorAge
* SHA256E is new default backendGravatar Joey Hess2012-09-12
| | | | | | | | The default backend used when adding files to the annex is changed from SHA256 to SHA256E, to simplify interoperability with OSX, media players, and various programs that needlessly look at symlink targets. To get old behavior, add a .gitattributes containing: * annex.backend=SHA256
* use SHA256 by defaultGravatar Joey Hess2011-11-04
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* update to not overstate the danger or WORMGravatar Joey Hess2011-08-29
|
* update documentation for new, neutered key-value backendsGravatar Joey Hess2011-08-28
| | | | | | | | | | | Backends are now only used to generate keys (and check them); they are not arbitrary key-value stores for data, because it turned out such a store is better modeled as a special remote. Updated docs to not imply backends do more than they do now. Sometimes I'm tempted to rename "backend" to "keytype" or something, which would really be more clear. But it would be an annoying transition for users, with annex.backends etc.
* wordingGravatar Joey Hess2011-07-01
|
* updates for web remote and removing URL backendGravatar Joey Hess2011-07-01
|
* Added filename extension preserving variant backends SHA1E, SHA256E, etc.Gravatar Joey Hess2011-05-16
|
* document S3 remotesGravatar Joey Hess2011-03-27
|
* doc updateGravatar Joey Hess2011-03-27
|
* New backends: SHA512 SHA384 SHA256 SHA224Gravatar Joey Hess2011-03-01
|
* The git-annex-backend attribute has been renamed to annex.backend.Gravatar Joey Hess2010-11-28
|
* Merge branch 'master' into checkoutGravatar Joey Hess2010-11-09
|\ | | | | | | | | | | Conflicts: debian/changelog doc/backends.mdwn
| * reorg .git/annexGravatar Joey Hess2010-11-08
| |
* | documentation for checkoutGravatar Joey Hess2010-11-07
|/
* expand docsGravatar Joey Hess2010-11-01
|
* warning about sha1Gravatar Joey Hess2010-10-27
|
* updateGravatar Joey Hess2010-10-19