Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150876034
**[Test build #1953 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1953/consoleFull)**
for PR 9250 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150876266
Merged to master/1.5
---
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
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150852862
All for now. Merge at will. Thanks.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150857893
**[Test build #1953 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1953/consoleFull)**
for PR 9250 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9250
---
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 feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150647882
+1
If you are doing a lot of these, it'd be great to batch them. Don't be
mistaken - the effort is hugely appreciated!
---
If your project is set up for it, you
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150615913
If it's a handful of typos I wouldn't bother with a JIRA. I think the
operating theory is JIRA = what and PR = how, and if those are virtually the
same there's no point
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150561484
Can one of the admins verify this patch?
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150562364
**[Test build #1945 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1945/consoleFull)**
for PR 9250 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150561806
To lower the overhead, maybe you can take a pass over all of the project to
detect typos? a spell-checker will turn up way too many false positives, but
half an hour
GitHub user jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/9250
Fix typos
Two typos squashed.
BTW Let me know how to proceed with other typos if I ran across any. I
don't feel well to leave them aside as much as sending pull requests with such
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150674296
Yeah that's fine, I think Scala files may be too much to bear. I just use
the spell-checker in the IDE as I find it a little easier to manage. Docs are
indeed higher
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150606925
Ok, deal. I can run a spell-checker and see what I can fix within a
half-an-hour timeframe. Should I go and create a JIRA task for it? Any
particular
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150594861
Disregard the failure, it's unrelated
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150594621
**[Test build #1945 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1945/consoleFull)**
for PR 9250 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150708006
@jaceklaskowski is this ready to be merged or are you waiting to submit
more?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/9250#issuecomment-150659267
Thanks @rxin @srowen for support! It took me 30 minutes to find and use
`aspell` on a single Scala package and it drove me crazy with tons of false
positives -
17 matches
Mail list logo