Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Added a comment | 2015-05-19 | |
| | |||
* | (no commit message) | 2015-05-19 | |
| | |||
* | Added a comment: A possible solution | 2015-05-19 | |
| | |||
* | Added a comment: Convert bare repository to normal | 2015-05-19 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-05-17 | |
|\ | |||
* | | webapp: Fix zombie xdg-open process left when opening file browser. Closes: ↵ | 2015-05-17 | |
| | | | | | | | | #785498 | ||
* | | comment typos | 2015-05-17 | |
| | | |||
| * | fix links | 2015-05-16 | |
| | | |||
| * | Added a comment | 2015-05-16 | |
| | | |||
| * | finally open that discussion directly | 2015-05-16 | |
| | | |||
* | | twitter search seems to be too broken to include a feed from it anymore | 2015-05-16 | |
| | | | | | | | | | | | | The search seems to only find spammy tweets. I know people talk about git-anenx on twitter, but it seems twitter's search does not find those interesting conversations. | ||
| * | Added a comment | 2015-05-16 | |
| | | |||
* | | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-05-16 | |
|\| | |||
* | | nasty issue with fcntl locks | 2015-05-16 | |
| | | |||
| * | Added a comment: Disaster recovery | 2015-05-15 | |
| | | |||
| * | Added a comment: git annex repair --force | 2015-05-15 | |
| | | |||
| * | (no commit message) | 2015-05-15 | |
| | | |||
| * | (no commit message) | 2015-05-15 | |
| | | |||
| * | Added a comment: mailing lists and support sites | 2015-05-14 | |
| | | |||
| * | json missing some output? | 2015-05-14 | |
|/ | |||
* | devblog | 2015-05-14 | |
| | |||
* | fix type in the name of --used-refspec in changelog | 2015-05-14 | |
| | |||
* | add annex.used-refspec | 2015-05-14 | |
| | |||
* | unused: Add --used option, which can specify a set of refs to consider used, ↵ | 2015-05-14 | |
| | | | | rather than the default of considering all refs used. | ||
* | adjust fast build so that ./ghci works with ghc 7.8.4 | 2015-05-14 | |
| | |||
* | more formal spec | 2015-05-14 | |
| | |||
* | Added a comment | 2015-05-14 | |
| | |||
* | Added a comment: confirmed | 2015-05-14 | |
| | |||
* | Added a comment | 2015-05-14 | |
| | |||
* | Added a comment: transcript | 2015-05-14 | |
| | |||
* | response | 2015-05-13 | |
| | |||
* | design | 2015-05-13 | |
| | |||
* | update | 2015-05-12 | |
| | |||
* | Stale transfer lock and info files will be cleaned up automatically when ↵ | 2015-05-12 | |
| | | | | | | get/unused/info commands are run. Deleting lock files is tricky, tricky stuff. I think I got it right! | ||
* | don't clean up transfer lock file when retrying transfer | 2015-05-12 | |
| | | | | | This affected callers that used forwardRetry; if the 1st attempt failed it would clean up the transfer lock before retrying. | ||
* | Fix an unlikely race that could result in two transfers of the same key ↵ | 2015-05-12 | |
| | | | | | | running at once. As discussed in bug report. | ||
* | convert to using Utility.Lockfile for transfer lock files | 2015-05-12 | |
| | | | | | | | | Should be no behavior changes, just simplified code. The only actual difference is it doesn't truncate the lock file. I think that was a holdover from when transfer info was written to the lock file. | ||
* | an optimization that also fixes a reversion | 2015-05-12 | |
| | | | | | | | | | | | | | | | | | | | | This is a little optimisation; avoid loading the info file for the download of the current key when checking for other downloads. The reversion it fixes is sorta strange. b94eafec8c4a7868da753f9b22ca823552e9764c broke checking for transfers that were already in progress. Indeed, the transfer lock was not held after getTransfers was called. Why? I think it's magic in ghc's handling of getLock and setLock, although it's hard to tell since those functions are almost entirely undocumented as to their semantics. Something, either the RTS (or maybe it's linux?) notices that the same process has taken a lock and is now calling getLock on a FD attached to the same file. So, it drops the lock. So, this optimisation avoids that problematic behavior. | ||
* | devblog | 2015-05-12 | |
| | |||
* | Avoid accumulating transfer failure log files unless the assistant is being ↵ | 2015-05-12 | |
| | | | | | | | | | | | | used. Only the assistant uses these, and only the assistant cleans them up, so make only git annex transferkeys write them, There is one behavior change from this. If glacier is being used, and a manual git annex get --from glacier fails because the file isn't available yet, the assistant will no longer later see that failed transfer file and retry the get. Hope no-one depended on that old behavior. | ||
* | Take space that will be used by running downloads into account when checking ↵ | 2015-05-12 | |
| | | | | annex.diskreserve. | ||
* | update | 2015-05-12 | |
| | |||
* | allow building without ascii-progress, since it is not ready yet | 2015-05-12 | |
| | | | | No progress bars with -J unless built with ascii-progress. | ||
* | Merge branch 'master' into concurrentprogress | 2015-05-12 | |
|\ | | | | | | | | | | | | | | | | | | | | | | | Conflicts: Command/Fsck.hs Messages.hs Remote/Directory.hs Remote/Git.hs Remote/Helper/Special.hs Types/Remote.hs debian/changelog git-annex.cabal | ||
| * | note about git annex drop behavior change in bare repo | 2015-05-12 | |
| | | |||
| * | Merge branch 'master' of ssh://git-annex.branchable.com | 2015-05-12 | |
| |\ | |||
| * | | drop: Now supports --all, --unused, and --key. | 2015-05-12 | |
| | | | |||
| | * | (no commit message) | 2015-05-12 | |
| | | | |||
| | * | Added a comment: Create symlink in the root directory | 2015-05-12 | |
| | | | |||
| | * | Added a comment | 2015-05-12 | |
| | | |