summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* releasing version 3.201111053.20111105Gravatar Joey Hess2011-11-05
|
* add bug reportGravatar Valentin_Haenel2011-11-05
|
* Pass -t to rsync to preserve timestamps.Gravatar Joey Hess2011-11-04
|
* a recipe for setting up a bare remoteGravatar Valentin_Haenel2011-11-04
|
* Added a comment: depends ...Gravatar http://joey.kitenet.net/2011-11-04
|
* 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.
* add changelog for bugfixGravatar Joey Hess2011-11-04
|
* fix linkGravatar Joey Hess2011-11-04
|
* (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo2011-11-03
|
* ensure directory exists when locking journalGravatar Joey Hess2011-11-02
| | | | | Fixes git annex init in a bare repository that already has a git-annex branch.
* tweakGravatar Joey Hess2011-11-02
|
* Record uuid when auto-initializing a remote so it shows in status.Gravatar Joey Hess2011-11-02
|
* add tip for mode of operation somewhat like mercurial bigfiles extensionGravatar Joey Hess2011-11-02
|
* point to new extension now in mercurialGravatar Joey Hess2011-11-02
|
* playing with >=>Gravatar Joey Hess2011-10-31
| | | | | Apparently in haskell if you teach a man to fish, he'll write more pointfree code.
* cleanupGravatar Joey Hess2011-10-31
|
* fixed my build environmentGravatar Joey Hess2011-10-31
|
* better command nameGravatar Joey Hess2011-10-31
|
* cleanupGravatar Joey Hess2011-10-31
|
* The fromkey command now takes the key as its first parameter. The --key ↵Gravatar Joey Hess2011-10-31
| | | | option is no longer used.
* Removed the setkey command, and added a setcontent command with a more ↵Gravatar Joey Hess2011-10-31
| | | | useful interface.
* cleanupGravatar Joey Hess2011-10-31
|
* closuresGravatar Joey Hess2011-10-30
|
* update; status is no longer slowGravatar Joey Hess2011-10-30
|
* closuresGravatar Joey Hess2011-10-30
|
* add command name to some outputGravatar Joey Hess2011-10-30
|
* refactoring and cleanupGravatar Joey Hess2011-10-30
| | | | No code changes.
* bare cleanupGravatar Joey Hess2011-10-29
|
* unused, dropunused: Now work in bare repositories.Gravatar Joey Hess2011-10-29
| | | | | Turned out I had already done all the work needed to support this when unused started checking all branches.
* status: clean up for bare repositoriesGravatar Joey Hess2011-10-29
| | | | | | | | | | The backend usage graph shows present keys as well as keys found in the repository tree, so it will also be populated for bare repositories. Changed wording to "visible annex keys", which explains why it's 0 in a bare repository (no keys visible as no tree), and also why it varies depending on which branch is checked out. This seemed better than doing something expensive to look up keys from the git-annex branch.
* refactorGravatar Joey Hess2011-10-29
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-10-29
|\
* | fsck: Now works in bare repositories.Gravatar Joey Hess2011-10-29
| | | | | | | | | | | | | | | | | | Checks location log information, and file contents. Does not check that numcopies is satisfied, as .gitattributes information about numcopies is not available in a bare repository. In practice, that should not be a problem, since fsck is also run in a checkout and will check numcopies there.
| * (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U2011-10-29
| |
* | refactorGravatar Joey Hess2011-10-29
|/
* getting tired of repeating myselfGravatar Joey Hess2011-10-29
|
* (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U2011-10-29
|
* responsenGravatar Joey Hess2011-10-29
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-10-29
|\
* | add a tipGravatar Joey Hess2011-10-29
| |
* | clean up check selection codeGravatar Joey Hess2011-10-29
| | | | | | | | | | | | | | | | | | This new approach allows filtering out checks from the default set that are not appropriate for a command, rather than having to list every check that is appropriate. It also reduces some boilerplate. Haskell does not define Eq for functions, so I had to go a long way around with each check having a unique id. Meh.
| * (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U2011-10-29
| |
| * Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U2011-10-29
|/
* responsenGravatar Joey Hess2011-10-29
|
* (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U2011-10-29
|
* (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U2011-10-29
|
* closeGravatar Joey Hess2011-10-29
|
* sheesh. seriously?Gravatar Joey Hess2011-10-29
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2011-10-29
|\
* | pebakGravatar Joey Hess2011-10-29
| |