Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Added a comment | 2012-10-16 | |
| | |||
* | Added a comment | 2012-10-16 | |
| | |||
* | Added a comment | 2012-10-16 | |
| | |||
* | removed | 2012-10-16 | |
| | |||
* | Added a comment | 2012-10-16 | |
| | |||
* | Added a comment | 2012-10-16 | |
| | |||
* | Added a comment | 2012-10-16 | |
| | |||
* | Added a comment | 2012-10-16 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2012-10-16 | |
|\ | |||
* | | blog for the day | 2012-10-16 | |
| | | |||
| * | removed | 2012-10-16 | |
| | | |||
| * | Added a comment | 2012-10-16 | |
| | | |||
| * | Added a comment | 2012-10-16 | |
|/ | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2012-10-16 | |
|\ | |||
| * | Added a comment | 2012-10-16 | |
| | | |||
* | | A relative core.worktree is relative to the gitdir. | 2012-10-16 | |
| | | | | | | | | | | | | | | | | Now that this is handled correctly, git-annex can be used in git submodules. Also, fixed infelicity where Git.CurrentRepo and Git.Config.updateLocation were both dealing with core.worktree. Now updateLocation handles it for Local as well as for LocalUnknown repos. | ||
| * | Added a comment | 2012-10-16 | |
| | | |||
| * | Added a comment | 2012-10-16 | |
| | | |||
| * | (no commit message) | 2012-10-16 | |
| | | |||
| * | (no commit message) | 2012-10-16 | |
|/ | |||
* | Bug fix: A recent change caused git-annex-shell to crash. | 2012-10-15 | |
| | |||
* | (no commit message) | 2012-10-16 | |
| | |||
* | poll vote (Tahoe-LAFS) | 2012-10-16 | |
| | |||
* | disable ssh connection caching for standalone builds | 2012-10-15 | |
| | | | | | | | | | | | | The standalone build does not bundle its own ssh, so should be built to support as wide an array of ssh versions as possible, so turn off connection caching. Unfortunatly, as implemented this forces a full rebuild when building the standalone binary, and of course it makes it somewhat slower. This is not ideal, but neither is probing the ssh version every time it's run (slow), or once when initializing a repo (fragile). | ||
* | Added a comment | 2012-10-15 | |
| | |||
* | (no commit message) | 2012-10-15 | |
| | |||
* | (no commit message) | 2012-10-15 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2012-10-14 | |
|\ | |||
* | | blog for the day | 2012-10-14 | |
| | | |||
* | | logic error | 2012-10-14 | |
| | | |||
* | | handle transfer repository bootstrapping | 2012-10-14 | |
| | | | | | | | | | | | | | | | | When there's just 1 client repo, and a transfer repo is created, its preferred content will now make it prefer all content in the client, even though there's no other client yet to transfer it to. Presumably, another client will be created eventually. It might even already exist, and the transfer repo will be used to connect up with it. | ||
| * | poll vote (OpenStack SWIFT) | 2012-10-14 | |
| | | |||
* | | update | 2012-10-14 | |
| | | |||
* | | fix display of transfers for remotes not in syncRemotes list | 2012-10-14 | |
| | | |||
* | | avoid queuing transfers for remotes after syncing to them is paused | 2012-10-14 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | This avoids the expensive transfer scan relying on its list of remotes to scan being accurate throughout, which it will not be when the user pauses syncing to a remote. I feel it's ok to queue transfers to *any* known remote, not just the ones being scanned. Note that there are still small races where after syncing to a remote is paused, a transfer can be queued for it. Not just in the expensive transfer scan, but in the cheap failed transfer scan, and elsewhere. | ||
| * | poll vote (Google Drive) | 2012-10-14 | |
| | | |||
| * | poll vote (My phone (or MP3 player)) | 2012-10-14 | |
| | | |||
| * | Added a comment: Thank you for stickers | 2012-10-14 | |
| | | |||
| * | poll vote (Tahoe-LAFS) | 2012-10-14 | |
|/ | |||
* | add help command | 2012-10-13 | |
| | |||
* | (no commit message) | 2012-10-13 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2012-10-13 | |
|\ | |||
* | | full analysis of ways content could stop being preferred and need to be dropped | 2012-10-13 | |
| | | |||
| * | Added a comment: Asynchronous hooks? | 2012-10-13 | |
| | | |||
| * | poll vote (My phone (or MP3 player)) | 2012-10-13 | |
| | | |||
| * | poll vote (My phone (or MP3 player)) | 2012-10-13 | |
|/ | |||
* | blog for the day | 2012-10-12 | |
| | |||
* | poll vote (Tahoe-LAFS) | 2012-10-12 | |
| | |||
* | poll vote (Tahoe-LAFS) | 2012-10-12 | |
| | |||
* | poll vote (Tahoe-LAFS) | 2012-10-12 | |
| |