Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1056#issuecomment-47065707
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1056#issuecomment-47065717
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1056#issuecomment-47065241
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16106/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1056#issuecomment-47065240
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1056#issuecomment-47065129
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1056#issuecomment-47065134
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 have
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/1056#issuecomment-47065070
Uploaded a new patch that adds a general executor->driver heartbeat. With
the patch, observed jobs running fine on a pseudo-distributed yarn cluster.
---
If your project
Github user rahulsinghaliitd commented on the pull request:
https://github.com/apache/spark/pull/1094#issuecomment-47064230
@vanzin I was only referring to how the UI URL is passed around. I have
used the longer way of passing it around using command line arguments whereas
the other c
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47063649
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47063650
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16104/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-47063423
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16105/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-47063421
Merged build finished.
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47062643
OK, I reproduced it locally by running `PruningSuite` after
`HiveCompatibilitySuite`. Investigating.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-47062485
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-47062480
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1140#issuecomment-47061957
Jenkins, test this please. @sebastienrainville thanks! Did you test this by
chance on your cluster? Unfortunately our test coverage is not good here.
In a relate
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47061886
@marmbrus Would you mind to retest this? 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/1208#issuecomment-47061859
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16103/
---
If your project is set up for it, you can
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47061848
Weird, I can't reproduce the test failure locally, and the failed test case
seems completely unrelated to the change...
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1208#issuecomment-47061857
Merged build finished.
---
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 hav
Github user li-zhihui commented on the pull request:
https://github.com/apache/spark/pull/900#issuecomment-47061333
@tgravescs
I add a new commit that move waitBackendReady from DAGScheduler.submitStage
to TaskSchedulerImpl.submitTasks, for 2 reasons
* Optimize performanc
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1207#issuecomment-47060997
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1207#issuecomment-47060999
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16102/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47060998
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16101/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47060996
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47059590
Oh, Jenkins is working. :)
---
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/1190#issuecomment-47059533
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47059529
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 h
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47059507
@rxin , can you ask Jenkins to retest this? Seems he doesn't answer me. :)
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1190#issuecomment-47059380
Jenkins, retest 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 n
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47058605
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16094/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1206#issuecomment-47058602
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47058606
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16100/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47058598
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47058601
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47058599
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47058600
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47058607
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16095/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1206#issuecomment-47058608
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16097/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47058604
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16096/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-47058414
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16093/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-47058413
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1208#issuecomment-47057882
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1208#issuecomment-47057887
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 have
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/1208
SPARK-1470: Use the scala-logging wrapper instead of the directly sfl4j api
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-1470
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/332
---
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 enable
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1207#issuecomment-47057495
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1207#issuecomment-47057501
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 have
GitHub user dbtsai opened a pull request:
https://github.com/apache/spark/pull/1207
SPARK-2272 [MLlib] Feature scaling which standardizes the range of
independent variables or features of data
Feature scaling is a method used to standardize the range of independent
variables or fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47057109
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47057114
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 have
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47056934
@rxin Done
---
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
en
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1153#issuecomment-47056690
This PR is the subsequent optimization of #713 ,should only merge to the
master.
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47056628
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47056630
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16091/
---
If your project
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/1205#discussion_r14167633
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveQuerySuite.scala
---
@@ -370,6 +370,16 @@ class HiveQuerySuite extends HiveCompar
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1153#issuecomment-47056376
@witgo mind merging this to 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47056372
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16090/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47056371
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47056256
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47056247
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 h
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47056084
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 thi
Github user concretevitamin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1205#discussion_r14167337
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveQuerySuite.scala
---
@@ -370,6 +370,16 @@ class HiveQuerySuite extends Hive
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47055992
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16099/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47055991
Merged build finished.
---
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 hav
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-4702
SGTM. We should probably switch to this:
https://issues.apache.org/jira/browse/HIVE-6017 although it is a lower priority
task (although for the purpose of API compatibility,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47055506
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1112#issuecomment-47055497
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 h
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47055461
@rxin we are probably using scala's but this code is unwrapping values that
come from hive.
---
If your project is set up for it, you can reply to this email and have y
Github user sebastienrainville commented on the pull request:
https://github.com/apache/spark/pull/1140#issuecomment-47055352
There you go, I pushed the requested change. It should be ready to go now.
---
If your project is set up for it, you can reply to this email and have your
repl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47055279
Aren't we using Scala's BigDecimal?
---
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/1197#issuecomment-47055252
Merged build finished.
---
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47055253
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16098/
---
If your project is set up for it, you can
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1194
---
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 enab
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47054937
Mind changing the title to say "SPARK" instead of "SARPK"?
---
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 li-zhihui commented on a diff in the pull request:
https://github.com/apache/spark/pull/900#discussion_r14166951
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -46,9 +46,14 @@ class CoarseGrainedSchedulerBack
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47054710
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47054705
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 h
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1204
---
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 enab
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1204#issuecomment-47054665
Looks good. Merging in master & branch-1.0.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1197#issuecomment-47054592
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1185
---
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 enab
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1185#issuecomment-47054432
Great, thanks! I've merged this with a slight modification to the message.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1206#issuecomment-47054266
@johnynek We probably want chill to handle this out of the box. Let me know
if this is the appropriate fix and I can submit a PR for chill too.
---
If your project is set
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1206#issuecomment-47054020
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1206#issuecomment-47054013
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 h
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/1206
[SPARK-2270] Kryo cannot serialize results returned by asJavaIterable
and thus groupBy/cogroup are broken in Java APIs when Kryo is used).
@pwendell this should be merged into 1.0.1.
You can m
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47053762
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47053751
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47053675
Merged build finished.
---
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 hav
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47053691
Jenkins, retest 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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47053676
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16092/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47053498
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47053493
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1205#issuecomment-47053489
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1199#issuecomment-47053491
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47053239
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-47053240
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1202#issuecomment-47053227
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-47053228
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 h
1 - 100 of 363 matches
Mail list logo
