summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* (no commit message)Gravatar olaf2017-08-15
|
* Added a commentGravatar olaf2017-08-15
|
* ideaGravatar Joey Hess2017-08-15
|
* hmmGravatar Joey Hess2017-08-15
|
* responses, bug I noticedGravatar Joey Hess2017-08-15
|
* commentGravatar Joey Hess2017-08-15
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2017-08-15
|\
* | Disable http-client's default 30 second response timeout when HEADing an url ↵Gravatar Joey Hess2017-08-15
| | | | | | | | to check if it exists. Some web servers take quite a long time to answer a HEAD request.
* | forwardedGravatar Joey Hess2017-08-15
| |
* | commentGravatar Joey Hess2017-08-15
| |
* | commentGravatar Joey Hess2017-08-15
| |
* | commentGravatar Joey Hess2017-08-15
| |
* | move, copy: Support --batch.Gravatar Joey Hess2017-08-15
| |
| * (no commit message)Gravatar olaf2017-08-15
|/
* test: Avoid most situations involving failure to delete test directoriesGravatar Joey Hess2017-08-14
| | | | | | | | | | | | | | | | | | | By forking a worker process and only deleting the test directory once it exits. This way, if a test leaves files open, they'll get closed when the worker exits, so avoiding failure to delete open files on Windows, and failure to delete directories due to NFS lock files. If a test leaves a git worker process running, the closed pipes should cause the worker to exit too, also avoiding the problem there. The 10 second sleep ought to give plenty of time for such worker processes to exit, although this is of course a race. Finally, even if test directory fails to be deleted still, it won't appear as if the last test in the test suite failed; the error will be displayed at the very end. This commit was supported by the NSF-funded DataLad project.
* Fix a git-annex test failure when run on NFS due to NFS lock files ↵Gravatar Joey Hess2017-08-14
| | | | | | | | | | | | | preventing directory removal. Should fix this: lock (v6 --force): FAIL Exception: .git/annex/keys: removeDirectoryRecursive: unsatisfied constraints (Directory not empty) Verified that the test case still catches the regression it's meant to. This commit was supported by the NSF-funded DataLad project.
* avoid accidental Show of VectorClockGravatar Joey Hess2017-08-14
| | | | Removed its Show instance.
* Added GIT_ANNEX_VECTOR_CLOCK environment variableGravatar Joey Hess2017-08-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Can be used to override the default timestamps used in log files in the git-annex branch. This is a dangerous environment variable; use with caution. Note that this only affects writing to the logs on the git-annex branch. It is not used for metadata in git commits (other env vars can be set for that). There are many other places where timestamps are still used, that don't get committed to git, but do touch disk. Including regular timestamps of files, and timestamps embedded in some files in .git/annex/, including the last fsck timestamp and timestamps in transfer log files. A good way to find such things in git-annex is to get for getPOSIXTime and getCurrentTime, although some of the results are of course false positives that never hit disk (unless git-annex gets swapped out..) So this commit does NOT necessarily make git-annex comply with some HIPPA privacy regulations; it's up to the user to determine if they can use it in a way compliant with such regulations. Benchmarking: It takes 0.00114 milliseconds to call getEnv "GIT_ANNEX_VECTOR_CLOCK" when that env var is not set. So, 100 thousand log files can be written with an added overhead of only 0.114 seconds. That should be by far swamped by the actual overhead of writing the log files and making the commit containing them. This commit was supported by the NSF-funded DataLad project.
* (no commit message)Gravatar pitsa@5f5d24a1fb7ba0d050ae7cf95b4c3032002e8e382017-08-13
|
* Added a commentGravatar https://launchpad.net/~liori2017-08-12
|
* Added a commentGravatar yarikoptic2017-08-12
|
* initial whining about 2 ssh promptsGravatar yarikoptic2017-08-12
|
* Added a comment: Git HistoryGravatar xloem2017-08-10
|
* Added a comment: relates to being on NFSGravatar yarikoptic2017-08-09
|
* Added a comment: comes and goes!Gravatar yarikoptic2017-08-09
|
* Added a comment: "reproduces" in a complete git installationGravatar yarikoptic2017-08-09
|
* (no commit message)Gravatar Tafnzart2017-08-09
|
* Added a comment: 6.20170101 - still unable.Gravatar aer1PheiZa2017-08-07
|
* Added a comment: "WSL adds inotify & filesystem change notification support"Gravatar https://openid.stackexchange.com/user/26f3c692-0460-4cbc-8712-e9bfb5889fb22017-08-07
|
* updateGravatar Joey Hess2017-08-06
|
* Added a commentGravatar https://launchpad.net/~liori2017-08-04
|
* Added a commentGravatar jakemagee2017-08-02
|
* (no commit message)Gravatar yarikoptic2017-08-02
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2017-08-01
|\
* | commentGravatar Joey Hess2017-08-01
| |
| * removedGravatar yarikoptic2017-08-01
| |
| * Added a commentGravatar yarikoptic2017-08-01
| |
| * Added a commentGravatar yarikoptic2017-08-01
| |
| * (no commit message)Gravatar jakemagee2017-07-31
| |
| * Added a commentGravatar yarikoptic2017-07-31
|/
* responseGravatar Joey Hess2017-07-31
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2017-07-31
|\
* | commentGravatar Joey Hess2017-07-31
| |
| * Added a comment: issue seems to be out thereGravatar yarikoptic2017-07-31
| |
| * (no commit message)Gravatar lykos2017-07-30
| |
| * (no commit message)Gravatar lykos2017-07-30
| |
| * (no commit message)Gravatar lykos2017-07-30
| |
| * (no commit message)Gravatar lykos2017-07-30
| |
| * Added a comment: pipe: resource exhausted (Too many open files)Gravatar ilovezfs2017-07-30
| |
| * initial bug reportGravatar yarikoptic2017-07-30
|/