Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/700
All tests pass with `docker/build.sh -t -n -i`
VOTE +1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project d
Github user okram commented on the issue:
https://github.com/apache/tinkerpop/pull/700
```
[INFO]
[INFO] BUILD SUCCESS
[INFO]
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/700
`docker/build.sh -t -i` succeeded.
VOTE: +1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user okram commented on the issue:
https://github.com/apache/tinkerpop/pull/700
No. I just spaced on selecting `tp32/` and left it defaulted at `master/`.
Fixed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/700
Any reason why this shouldn't go into `tp32/`?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this f
