Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8494#issuecomment-135637877
[Test build #41720 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41720/console)
for PR 8494 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8455#discussion_r38171523
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -30,6 +30,7 @@ import org.apache.spark.sql.{DataFrame, Row}
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8455#issuecomment-135637836
LGTM except the comment above. I'll merge it after 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.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8494#issuecomment-135638024
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135640246
I'd follow postgres here.
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/6599#issuecomment-135598700
I think that we should also backport this to branch-1.4.
+1 since we fix it in 1.5.0. Just confirmed this one didn't have conflicts
with branch-1.4.
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135603859
[Test build #41717 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41717/consoleFull)
for PR 8464 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38166499
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/local/LimitNode.scala ---
@@ -0,0 +1,45 @@
+/*
+* Licensed to the Apache Software
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-135615906
Alright I'm going to merge this as its better to do so before more breaking
style changes get in. Will watch Jenkins for the next couple of hours to make
sure things
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/8125#discussion_r38167285
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/CombineSmallFile.scala ---
@@ -0,0 +1,43 @@
+/*
+ * Licensed to the Apache
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135616119
Thanks @lresende -- 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135620132
[Test build #41718 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41718/console)
for PR 8343 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8494#issuecomment-135620007
[Test build #41720 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41720/consoleFull)
for PR 8494 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8495#issuecomment-135621721
[Test build #41722 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41722/consoleFull)
for PR 8495 at commit
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8495#issuecomment-135624869
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
enabled
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8493#issuecomment-135629824
[Test build #41716 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41716/console)
for PR 8493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8493#issuecomment-135629856
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/8493#issuecomment-135629857
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8271#issuecomment-135638595
I think this requires some micro-benchmark. I want to see the overhead of
additional two checks. We can also test a single `require` statement that
contains both checks.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8362#issuecomment-135639349
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/8362#issuecomment-135639351
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135639367
Merging this in master branch-1.5. 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135595941
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8343#issuecomment-135595930
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8493#issuecomment-135601511
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8493#issuecomment-135601503
Merged build triggered.
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/8494#issuecomment-135618510
cc @marmbrus
---
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/8455#issuecomment-135637446
Merged build triggered.
---
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8118#discussion_r38171484
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/StopWordsRemover.scala ---
@@ -29,14 +29,14 @@ import org.apache.spark.sql.types.{ArrayType,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135637490
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/8455#issuecomment-135637464
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135637488
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/8455#issuecomment-135637651
[Test build #41728 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41728/consoleFull)
for PR 8455 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38164639
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/local/LimitNode.scala ---
@@ -0,0 +1,45 @@
+/*
+* Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135604744
[Test build #41711 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41711/console)
for PR 7878 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135604771
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/7878#issuecomment-135604767
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/8343#issuecomment-135617402
[Test build #41718 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41718/consoleFull)
for PR 8343 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8495#issuecomment-135620933
@yu-iskw I also found a minor bug in lint-r that I just fixed. Please let
me know if that is good. With this change lint-r passes on my machine
---
If your project is
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8455#discussion_r38169722
--- Diff: mllib/src/main/scala/org/apache/spark/ml/clustering/KMeans.scala
---
@@ -30,8 +30,11 @@ import org.apache.spark.sql.{DataFrame, Row}
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8492#issuecomment-135634760
From PostgresSQL:
```
If the array expression yields a null array, the result of ANY will be
null. If the left-hand expression yields null, the result of ANY is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135635298
Merged build triggered.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135635256
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8480#issuecomment-135366372
Yes, I think that commit was to pass style checks though. I assume this
doesn't fail anything? I mean, I don't mind just merging this, but in my
personal opinion I'd
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8451#issuecomment-135366571
The other sibling PRs look good and I can merge them. This looks good after
the `Strings` change.
---
If your project is set up for it, you can reply to this email and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8447
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8445
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8446
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135368814
[Test build #41676 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41676/console)
for PR 8464 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135368942
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/8464#issuecomment-135368946
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/8479#issuecomment-135369577
[Test build #1696 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1696/console)
for PR 8479 at commit
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/8464#discussion_r38080354
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/local/LocalNodeTest.scala
---
@@ -0,0 +1,192 @@
+/*
+* Licensed to the Apache
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/8481
[SPARK-SQL] [MINOR] Fixes typo in non-public HiveContext method name
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liancheng/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135370380
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135370354
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135370363
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135370350
Merged build triggered.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8479
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8464#issuecomment-135371382
[Test build #41681 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41681/consoleFull)
for PR 8464 at commit
Github user zerosign commented on the pull request:
https://github.com/apache/spark/pull/1297#issuecomment-135373104
Hi Ankur,
Any update on this pull request ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135304152
The normalization is not done by StructObjectInspector or
OrcStructObjectInspector, but in `SemanticAnalyzer` of Hive. I've checked with
Hive, even the orc
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8465
---
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 chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7520#discussion_r38065116
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/orc/OrcRelation.scala ---
@@ -253,7 +260,7 @@ private[orc] case class OrcTableScan(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135308659
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/7520#issuecomment-135308665
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/7520#issuecomment-135308292
[Test build #41671 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41671/console)
for PR 7520 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8465#issuecomment-135304194
Thanks - I've merged this.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135373483
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8481#issuecomment-135373539
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/8481#issuecomment-135373540
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/8481#issuecomment-135373462
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135374072
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/7520#issuecomment-135373958
[Test build #41677 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41677/console)
for PR 7520 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135376204
[Test build #41683 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41683/consoleFull)
for PR 8458 at commit
GitHub user romansew opened a pull request:
https://github.com/apache/spark/pull/8482
SPARK-10314 [CORE]RDD persist to OFF_HEAP tachyon got block rdd_x_x nâ¦
SPARK-10314 [CORE]RDD persist to OFF_HEAP tachyon got block rdd_x_x not
found exception when parallelism is big than data
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8482#issuecomment-135378312
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135384552
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135384520
Merged build triggered.
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135387576
/cc @JoshRosen @davies
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135388498
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135374076
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/8481#issuecomment-135374158
[Test build #41682 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41682/consoleFull)
for PR 8481 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135375355
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135375375
Merged build started.
---
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/8458#issuecomment-135376437
[Test build #41683 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41683/console)
for PR 8458 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8458#issuecomment-135376440
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/8458#issuecomment-135376439
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 CodingCat opened a pull request:
https://github.com/apache/spark/pull/8483
REMOVE spark.akka.failure-detector.threshold
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CodingCat/spark SPARK_10315
Alternatively you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135386761
[Test build #41684 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41684/consoleFull)
for PR 8483 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/8484
[SPARK-10065][SQL] Avoid triple copying of var-length objects in Array in
tungsten projection
JIRA: https://issues.apache.org/jira/browse/SPARK-10065
Currently we do unnecessary copying of
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135388747
@srowen , mind taking a look ?
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135388439
Merged build triggered.
---
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/8484#issuecomment-135389447
[Test build #41685 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41685/consoleFull)
for PR 8484 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135392719
[Test build #41684 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41684/console)
for PR 8483 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135392859
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/7520#issuecomment-135392980
One thing to note is that, case sensitivity of Spark SQL is configurable
([see here] [1]). So I don't think we should make `StructType` completely case
insensitive
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8483#issuecomment-135392861
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/8484#issuecomment-135394838
[Test build #41685 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41685/console)
for PR 8484 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8484#issuecomment-135394871
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
401 - 500 of 579 matches
Mail list logo
