summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Added a commentGravatar http://joeyh.name/2012-09-21
|
* updateGravatar Joey Hess2012-09-21
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2012-09-21
|\
* | fix breakage caught by test suiteGravatar Joey Hess2012-09-21
| | | | | | | | | | Can't use show-ref --tags --branches, as that omits remote branches. Instead, filter out the synced refs directly.
| * Added a comment: you rock! & roadmap update?Gravatar https://id.koumbit.net/anarcat2012-09-21
|/
* Added a commentGravatar http://joeyh.name/2012-09-21
|
* Added a commentGravatar http://www.davidhaslem.com/2012-09-21
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2012-09-20
|\
* | alernate, less crazy ideaGravatar Joey Hess2012-09-20
| |
* | a much crazier, but also more feasable ideaGravatar Joey Hess2012-09-20
| |
| * Added a commentGravatar http://joeyh.name/2012-09-20
|/
* ideaGravatar Joey Hess2012-09-20
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2012-09-20
|\
* | blog for the dayGravatar Joey Hess2012-09-20
| |
* | avoid calling the progress callback when the bytes sent have not changedGravatar Joey Hess2012-09-20
| | | | | | | | | | Does rsync stall and update its progress display? Dunno, but this was an easy optimisation to throw in.
* | watch for changes to transfer info files, to update progress bars on uploadGravatar Joey Hess2012-09-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This is handled differently for inotify, which can track modifications of existing files, and kqueue, which cannot (TTBOMK). On the inotify side, the TransferWatcher just waits for the file to be updated and reads the new bytesComplete. On the kqueue side, the TransferPoller has to re-read the file every update (currently 0.5 seconds, might need to increase that). I did think about working around kqueue's limitations by somehow creating a new file each time the size changed. But cleaning up all the files that would result seemed difficult. And really, this is not a lot worse than the TransferWatcher's behavior for downloads, which stats a file every 0.5 seconds. As long as the OS has decent file caching behavior..
| * Added a comment: can addurl use hashing once the file is downloaded?Gravatar https://www.google.com/accounts/o8/id?id=AItOawlc1og3PqIGudOMkFNrCCNg66vB7s-jLpc2012-09-20
| |
* | fix reading of transfer info files with a bytesComplete valueGravatar Joey Hess2012-09-20
| |
* | optimised rsync output reader to read whole blocks at a timeGravatar Joey Hess2012-09-20
| |
* | hook rsync special remote up to the progress reportingGravatar Joey Hess2012-09-20
| | | | | | | | | | | | | | | | Easy! Note that with an encrypted remote, rsync will be sending a little more data than the key size, so displayed progress may get to 100% slightly quicker than it should. I doubt this is a big enough effect to worry about.
* | updateGravatar Joey Hess2012-09-20
| |
* | upload progress bar for git remote on same filesystemGravatar Joey Hess2012-09-20
| | | | | | | | | | | | | | cp is used here, but we can just watch the size of the destination file This commit made from within the ruins of an old mill, overlooking a beautiful waterfall.
| * Added a commentGravatar http://joeyh.name/2012-09-20
|/
* Added a comment: Multiple annexes?Gravatar https://www.google.com/accounts/o8/id?id=AItOawlu-fdXIt_RF9ggvg4zP0yBbtjWQwHAMS42012-09-20
|
* poll vote (Amazon S3)Gravatar 193.22.163.22012-09-20
|
* poll vote (Amazon Glacier)Gravatar 193.22.163.22012-09-20
|
* poll vote (Google Drive)Gravatar 193.22.163.22012-09-20
|
* poll vote (My phone (or MP3 player))Gravatar 193.22.163.22012-09-20
|
* poll vote (Amazon S3)Gravatar 193.22.163.22012-09-20
|
* Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo2012-09-20
|
* poll vote (My phone (or MP3 player))Gravatar 92.207.74.1492012-09-20
|
* Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawlup4hyZo4eCjF8T85vfRXMKBxGj9bMdl02012-09-19
|
* typoGravatar Joey Hess2012-09-19
|
* better parameter nameGravatar Joey Hess2012-09-19
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2012-09-19
|\
* | blog for the dayGravatar Joey Hess2012-09-19
| |
* | recvkey is not an upload, so ignore the progress callbackGravatar Joey Hess2012-09-19
| |
* | rsync progress interceptionGravatar Joey Hess2012-09-19
| | | | | | | | | | | | | | | | Current implementation parses rsync's output a character a time, which is hardly efficient. It could be sped up a lot by using hGetBufSome, but that would require going really lowlevel, down to raw C style buffers (good example of that here: http://users.aber.ac.uk/afc/stricthaskell.html) But rsync doesn't output very much, so currently it seems ok.
| * Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus2012-09-19
| |
* | add a progress callback to storeKey, and threaded it all the way throughGravatar Joey Hess2012-09-19
| | | | | | | | | | | | | | | | Transfer info files are updated when the callback is called, updating the number of bytes transferred. Left unused p variables at every place the callback should be used. Which is rather a lot..
* | parser for rsync progress outputGravatar Joey Hess2012-09-19
| |
* | reorgGravatar Joey Hess2012-09-19
| |
* | renamed RsyncFile -> RsyncGravatar Joey Hess2012-09-19
| |
| * Added a commentGravatar http://joeyh.name/2012-09-19
| |
| * Added a commentGravatar http://joeyh.name/2012-09-19
|/
* add annex.delayadd configurationGravatar Joey Hess2012-09-19
|
* Added a commentGravatar http://joeyh.name/2012-09-19
|
* support old versions of git that do not have --allow-empty-messageGravatar Joey Hess2012-09-19
|
* add missing --no-verify to prevent the pre-commit hook's git annex fixGravatar Joey Hess2012-09-19
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2012-09-19
|\
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-05 12:47:02 +0000