Commit message (Collapse) | Author | Age | ||
---|---|---|---|---|
... | ||||
| * | (no commit message) | 2015-10-14 | ||
| | | ||||
| * | (no commit message) | 2015-10-14 | ||
| | | ||||
* | | word wrap | 2015-10-14 | ||
|/ | ||||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-10-14 | ||
|\ | ||||
* | | Changed drop ordering when using git annex sync --content or the assistant, ↵ | 2015-10-14 | ||
| | | | | | | | | to drop from remotes first and from the local repo last. This works better with the behavior changes to drop in many cases. | |||
| * | timing info | 2015-10-13 | ||
| | | ||||
* | | fix various build warnings, mostly on Windows | 2015-10-13 | ||
| | | | | | | | | And some when S3 is disabled | |||
| * | Added a comment | 2015-10-13 | ||
| | | ||||
* | | put Win32-extras in extra-deps as it's not yet in lts | 2015-10-13 | ||
| | | ||||
| * | more notes | 2015-10-13 | ||
| | | ||||
| * | workarounds | 2015-10-13 | ||
|/ | ||||
* | clarification | 2015-10-13 | ||
| | ||||
* | Added a comment | 2015-10-13 | ||
| | ||||
* | new bug | 2015-10-13 | ||
| | ||||
* | (no commit message) | 2015-10-13 | ||
| | ||||
* | doc/devblog/day_322-326__concurrent_drop_safety.mdwn: Wording | 2015-10-12 | ||
| | ||||
* | comment typo | 2015-10-12 | ||
| | ||||
* | fix windows build | 2015-10-12 | ||
| | ||||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-10-12 | ||
|\ | ||||
* | | fix export list to work on windows | 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 | ||
| | | ||||
* | | avoid ugly error about MVar if the sqlite worker thread crashes | 2015-10-12 | ||
| | | ||||
| * | (no commit message) | 2015-10-11 | ||
| | | ||||
| * | (no commit message) | 2015-10-11 | ||
| | | ||||
* | | use action, not sideAction | 2015-10-11 | ||
| | | | | | | | | | | | | | | | | sideAction is for things not generally related to the current action being performed. And, it adds a newline after the side action. This was not the right thing to use for stuff like "checksum", where doing a checksum is part of the git annex get process, and indeed we want it to display "(checksum...) ok" | |||
| * | 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 | ||
| | | | ||||
| * | | add inAnnex check to local lockKey | 2015-10-09 | ||
| | | | ||||
| * | | close bug | 2015-10-09 | ||
| | | | ||||
| * | | improve display when lockcontent fails | 2015-10-09 | ||
| | | | | | | | | | | | | | | | | | | | | | | | | /dev/null stderr; ssh is still able to display a password prompt despite this Show some messages so the user knows it's locking a remote, and knows if that locking failed. | |||
| * | | implement lockContent for ssh remotes | 2015-10-09 | ||
| | | | ||||
| * | | cleanup changelog | 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 | ||
| | | | ||||
| * | | fix local dropping to not require extra locking of copies, but only that the ↵ | 2015-10-09 | ||
| | | | | | | | | | | | | local copy be locked for removal | |||
| * | | improve message when drop failed due to no locked copy | 2015-10-09 | ||
| | | |