mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc update

Browse source
This commit is contained in:
Joey Hess 2011-03-27 17:30:44 -04:00
parent 45dbfbd02f
commit f8693facab
2 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
debian/changelog vendored
View file

@ -1,6 +1,8 @@
git-annex (0.20110326) UNRELEASED; urgency=low
* annex.diskreserve can be given in arbitrary units (ie "0.5 gigabytes")
* Generalized remotes handling, laying groundwork for remotes that are
not regular git remotes.
-- Joey Hess <joeyh@debian.org> Sat, 26 Mar 2011 14:36:16 -0400

9
doc/backends.mdwn
View file

@ -9,16 +9,13 @@ to retrieve the file's content (its value).
Multiple pluggable backends are supported, and a single repository
can use different backends for different files.
* `WORM` ("Write Once, Read Many") This backend stores the file's content
only in `.git/annex/objects/`, and assumes that any file with the same
basename, size, and modification time has the same content. So with
* `WORM` ("Write Once, Read Many") This backend assumes that any file with
the same basename, size, and modification time has the same content. So with
this backend, files can be moved around, but should never be added to
or changed. This is the default, and the least expensive backend.
* `SHA1` -- This backend stores the file's content in
`.git/annex/objects/`, with a name based on its sha1 checksum. This backend
* `SHA1` -- This backend uses a key based on a sha1 checksum. This backend
allows modifications of files to be tracked. Its need to generate checksums
can make it slower for large files.
for use.
* `SHA512`, `SHA384`, `SHA256`, `SHA224` -- Like SHA1, but larger
checksums. Mostly useful for the very paranoid, or anyone who is
researching checksum collisions and wants to annex their colliding data. ;)