[GitHub] spark pull request: Fix typo in WebUI

2015-11-03 Thread jaceklaskowski
GitHub user jaceklaskowski opened a pull request: https://github.com/apache/spark/pull/9444 Fix typo in WebUI You can merge this pull request into a Git repository by running: $ git pull https://github.com/jaceklaskowski/spark TImely-fix Alternatively you can review and

[GitHub] spark pull request: Fix typo in WebUI

2015-11-03 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/9444#issuecomment-153478248 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] spark pull request: Fix typo in WebUI

2015-11-03 Thread rxin
Github user rxin commented on the pull request: https://github.com/apache/spark/pull/9444#issuecomment-153522488 @jaceklaskowski I've merged this -- but might be better in the future to batch a bunch of typo fixes, since you are so great at finding them. --- If your project is set

[GitHub] spark pull request: Fix typo in WebUI

2015-11-03 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/9444 --- 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] spark pull request: Fix typo in WebUI

2015-11-03 Thread jaceklaskowski
Github user jaceklaskowski commented on the pull request: https://github.com/apache/spark/pull/9444#issuecomment-153579178 Thanks @rxin! I knew it might've been too small for a change, but since it's in the UI, I thought I'd *not* wait till I find other typos. --- If your project is

[GitHub] spark pull request: Fix typo in WebUI

2015-11-03 Thread rxin
Github user rxin commented on the pull request: https://github.com/apache/spark/pull/9444#issuecomment-153498285 Jenkins, test this please. --- 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