Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11702#issuecomment-196754018
Merged to master back to 1.4
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10242#issuecomment-196753549
**[Test build #53188 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53188/consoleFull)**
for PR 10242 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11702
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196752898
Merged build finished. Test FAILed.
---
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/11725#issuecomment-196752896
**[Test build #53186 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53186/consoleFull)**
for PR 11725 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196752899
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11702#issuecomment-196752770
I'm going to go ahead and merge. It passes, and clearly this change was
already intended to be in the source.
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196751935
**[Test build #53187 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53187/consoleFull)**
for PR 11724 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11725#issuecomment-196751981
**[Test build #53186 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53186/consoleFull)**
for PR 11725 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196751413
There should be a conflict with https://github.com/apache/spark/pull/11550.
I will resolve the conflict as soon as either this one or that one is
merged.
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/11725
[SPARK-13823] [CORE] More warnings, StandardCharset follow up
## What changes were proposed in this pull request?
Follow up to https://github.com/apache/spark/pull/11657
- Also
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-196749567
cc @rxin @falaki
---
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 HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/11724
[SPARK-13866][SQL] Handle decimal type in CSV inference at CSV data source.
## What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-13866
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196746553
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196746554
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196746337
**[Test build #53180 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53180/consoleFull)**
for PR 11717 at commit
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/10607#issuecomment-196746310
@sethah merged to master. Ping me when the remaining work on
[SPARK-12326](https://issues.apache.org/jira/browse/SPARK-12326) is ready for
review.
---
If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196746027
**[Test build #53185 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53185/consoleFull)**
for PR 11722 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10607
---
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11719#discussion_r56137442
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -557,7 +557,7 @@ private[spark] class TaskSetManager(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196743792
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196743793
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196743467
**[Test build #53179 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53179/consoleFull)**
for PR 11717 at commit
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/10355#discussion_r56136601
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/DecisionTreeClassifierSuite.scala
---
@@ -334,6 +334,51 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11723#issuecomment-196743359
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 MLnick commented on the pull request:
https://github.com/apache/spark/pull/10355#issuecomment-196743025
@BenFradet I'm ok with doing the other things like evaluators in a
different PR - however the only concern I'd have is it would temporarily break
things like
GitHub user hbhanawat opened a pull request:
https://github.com/apache/spark/pull/11723
[SPARK-13904][Scheduler]Add support for pluggable cluster manager
## What changes were proposed in this pull request?
This commit adds support for pluggable cluster manager. And also
Github user BenFradet commented on the pull request:
https://github.com/apache/spark/pull/10355#issuecomment-196742174
Surething
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11628#issuecomment-196741708
Here's an alternate take in light of comments above, to illustrate what I'm
thinking of:
```
...
val proc = pb.start()
val env =
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/10355#issuecomment-196741326
@BenFradet if it's not too much trouble, I think you can do
`AFTSurvivalRegression` and `IsotonicRegression` here.
---
If your project is set up for it, you can reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-196739239
**[Test build #53184 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53184/consoleFull)**
for PR 11722 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/11722
[SPARK-13903][SQL] Modify output nullability with constraints for Join
operator
## What changes were proposed in this pull request?
JIRA: https://issues.apache.org/jira/browse/SPARK-13903
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11628#discussion_r56134160
--- Diff: core/src/main/scala/org/apache/spark/rdd/PipedRDD.scala ---
@@ -176,6 +197,8 @@ private[spark] class PipedRDD[T: ClassTag](
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11628#discussion_r56133901
--- Diff: core/src/main/scala/org/apache/spark/rdd/PipedRDD.scala ---
@@ -176,6 +197,8 @@ private[spark] class PipedRDD[T: ClassTag](
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11628#discussion_r56133820
--- Diff: core/src/test/scala/org/apache/spark/rdd/PipedRDDSuite.scala ---
@@ -50,6 +50,29 @@ class PipedRDDSuite extends SparkFunSuite with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196733804
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196733060
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-196733132
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196733812
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-196733125
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196733050
Merged build finished. Test PASSed.
---
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/11716#issuecomment-196732579
**[Test build #53174 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53174/consoleFull)**
for PR 11716 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/11682#issuecomment-196732337
@gatorsmile Have you missed the special rule for Filter(Project()) ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-196732147
**[Test build #53178 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53178/consoleFull)**
for PR 11645 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196732103
**[Test build #53177 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53177/consoleFull)**
for PR 11716 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11721#issuecomment-196731895
**[Test build #53183 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53183/consoleFull)**
for PR 11721 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11658#issuecomment-196731812
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11658#issuecomment-196731814
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11658#issuecomment-196731413
**[Test build #53172 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53172/consoleFull)**
for PR 11658 at commit
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/11721
[SPARK-13885][YARN] Fix attempt id regression for Spark running on Yarn
## What changes were proposed in this pull request?
This regression is introduced in #9182, previously attempt id
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11701#issuecomment-196729627
Merged build finished. Test FAILed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11701#issuecomment-196729630
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11658#issuecomment-196728124
**[Test build #53182 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53182/consoleFull)**
for PR 11658 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-196728116
**[Test build #53181 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53181/consoleFull)**
for PR 11720 at commit
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/11720
[SPARK-13902][SCHEDULER] Make DAGScheduler.getAncestorShuffleDependencies()
return in topological order to ensure building ancestor stages first.
## What changes were proposed in this pull request?
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11701#issuecomment-196725160
**[Test build #53158 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53158/consoleFull)**
for PR 11701 at commit
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/11713#discussion_r56130697
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ApplicationMaster.scala ---
@@ -73,7 +73,8 @@ private[spark] class ApplicationMaster(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11714#issuecomment-196722804
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11714#issuecomment-196722803
Merged build finished. Test FAILed.
---
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/11714#issuecomment-196722691
**[Test build #53176 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53176/consoleFull)**
for PR 11714 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11714#issuecomment-196720214
Merged build finished. Test FAILed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11714#issuecomment-196720217
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11714#issuecomment-196719935
**[Test build #53175 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53175/consoleFull)**
for PR 11714 at commit
GitHub user trueyao opened a pull request:
https://github.com/apache/spark/pull/11719
[SPARK-13901][CORE]correct the logDebug information when jump to the next
locality level
JIRA Issue:https://issues.apache.org/jira/browse/SPARK-13901
In getAllowedLocalityLevel method of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11719#issuecomment-196719618
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/11717#issuecomment-196712964
**[Test build #53180 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53180/consoleFull)**
for PR 11717 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/11718#issuecomment-196712224
LGTM
---
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
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11371#issuecomment-196710904
I think the fundamental problem is, we give users the resolved attribute
but it may not be the real column when using it. For example, `b("count")`
actually is not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10428#issuecomment-196710771
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10428#issuecomment-196710774
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196710824
**[Test build #53179 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53179/consoleFull)**
for PR 11717 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11718#issuecomment-196710768
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/10428#issuecomment-196710599
**[Test build #53169 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53169/consoleFull)**
for PR 10428 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11717#issuecomment-196710196
cc @rxin @falaki
---
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 yucai opened a pull request:
https://github.com/apache/spark/pull/11718
[MINOR][TEST][SQL] Remove useless "expected" parameter
## What changes were proposed in this pull request?
Remove useless "expected" parameter in MathFunctionsSuite.scala's
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/11717
[SPARK-13899][SQL] Produce InternalRow instead of external Row at CSV data
source
## What changes were proposed in this pull request?
This PR makes CSV data source produce
Github user keypointt commented on the pull request:
https://github.com/apache/spark/pull/11703#issuecomment-196708955
Thanks a lot :+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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11703#issuecomment-196708862
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11703
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11703#issuecomment-196708860
Merged build finished. Test PASSed.
---
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/11703#issuecomment-196708709
**[Test build #53168 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53168/consoleFull)**
for PR 11703 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11703#issuecomment-196708575
Thanks - merging in master.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/11371#issuecomment-196707867
cc @cloud-fan
---
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
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196707519
LGTM
---
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
Github user rishitesh commented on a diff in the pull request:
https://github.com/apache/spark/pull/11645#discussion_r56125425
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/state/StateStoreRDD.scala
---
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9#issuecomment-196705344
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9#issuecomment-196705342
Merged build finished. Test PASSed.
---
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/9#issuecomment-196705247
**[Test build #53171 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53171/consoleFull)**
for PR 9 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-196704686
**[Test build #53178 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53178/consoleFull)**
for PR 11645 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11715#issuecomment-196704498
Merged build finished. Test FAILed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11715#issuecomment-196704499
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11715#issuecomment-196704336
**[Test build #53167 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53167/consoleFull)**
for PR 11715 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11544#issuecomment-196704355
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11544#issuecomment-196704353
Merged build finished. Test PASSed.
---
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/11544#issuecomment-196704221
**[Test build #53163 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53163/consoleFull)**
for PR 11544 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196703936
**[Test build #53177 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53177/consoleFull)**
for PR 11716 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11716#issuecomment-196703631
@cloud-fan Had an extra minute - I went ahead and removed analyzer as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11714#issuecomment-196702896
**[Test build #53176 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53176/consoleFull)**
for PR 11714 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11682
---
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/11714#issuecomment-196701472
I just merged #11682. Are there more?
---
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
701 - 800 of 875 matches
Mail list logo
