Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | new bug | 2015-10-13 | |
| | |||
* | (no commit message) | 2015-10-13 | |
| | |||
* | doc/devblog/day_322-326__concurrent_drop_safety.mdwn: Wording | 2015-10-12 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-10-12 | |
|\ | |||
* | | response | 2015-10-12 | |
| | | |||
* | | Avoid unncessary write to the location log when a file is unlocked and then ↵ | 2015-10-12 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | added back with unchanged content. Implemented with no additional overhead of compares etc. This is safe to do for presence logs because of their locality of change; a given repo's presence logs are only ever changed in that repo, or in a repo that has just been actively changing the content of that repo. So, we don't need to worry about a split-brain situation where there'd be disagreement about the location of a key in a repo. And so, it's ok to not update the timestamp when that's the only change that would be made due to logging presence info. | ||
| * | Added a comment | 2015-10-12 | |
| | | |||
* | | comment | 2015-10-12 | |
| | | |||
* | | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-10-12 | |
|\| | |||
* | | response | 2015-10-12 | |
| | | |||
* | | response | 2015-10-12 | |
| | | |||
* | | response | 2015-10-12 | |
| | | |||
* | | close | 2015-10-12 | |
| | | |||
| * | (no commit message) | 2015-10-11 | |
| | | |||
| * | (no commit message) | 2015-10-11 | |
| | | |||
| * | Added a comment | 2015-10-11 | |
| | | |||
| * | Added a comment | 2015-10-10 | |
| | | |||
| * | Added a comment | 2015-10-10 | |
| | | |||
| * | Added a comment | 2015-10-10 | |
|/ | |||
* | fix close tag | 2015-10-09 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-10-09 | |
|\ | |||
* \ | Merge branch 'dropproof' | 2015-10-09 | |
|\ \ | |||
* | | | massive devblog | 2015-10-09 | |
| | | | |||
| * | | close bug | 2015-10-09 | |
| | | | |||
| * | | also generate a drop safety proof for move --from remote | 2015-10-09 | |
| | | | |||
| * | | tests and verified that the bug is fixed, in all the cases I identified | 2015-10-09 | |
| | | | |||
| | * | (no commit message) | 2015-10-09 | |
| | | | |||
| | * | Added a comment: post-receive hook | 2015-10-09 | |
| | | | |||
| | * | removed | 2015-10-09 | |
| | | | |||
| | * | Added a comment | 2015-10-09 | |
| | | | |||
| | * | Added a comment | 2015-10-09 | |
| | | | |||
| | * | (no commit message) | 2015-10-09 | |
| | | | |||
| | * | Added a comment | 2015-10-09 | |
| | | | |||
| | * | (no commit message) | 2015-10-09 | |
| | | | |||
| | * | Added a comment: Sharing S3 bucket between repos | 2015-10-09 | |
| | | | |||
| * | | git-annex-shell: Added lockcontent command, to prevent dropping of key's ↵ | 2015-10-08 | |
|/ / | | | | | | | content. | ||
| * | Added a comment: ah -- the 32bit build I guess | 2015-10-08 | |
| | | |||
| * | Added a comment: standalone builds | 2015-10-08 | |
| | | |||
| * | Added a comment: Git Version | 2015-10-07 | |
| | | |||
| * | Added a comment | 2015-10-07 | |
| | | |||
| * | Added a comment | 2015-10-07 | |
|/ | |||
* | getting proof-y | 2015-10-07 | |
| | |||
* | titles | 2015-10-07 | |
| | |||
* | indents | 2015-10-07 | |
| | |||
* | alternative solution | 2015-10-07 | |
| | |||
* | analysis of some topologies, and idea to generate moves | 2015-10-07 | |
| | |||
* | copy --auto was checking the wrong repo's preferred content. (--from was ↵ | 2015-10-06 | |
| | | | | checking what --to should, and vice-versa.) Fixed this bug, which was introduced in version 5.20150727. | ||
* | analysis | 2015-10-06 | |
| | |||
* | comment | 2015-10-06 | |
| | |||
* | confirmed | 2015-10-06 | |
| |