Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12461#issuecomment-216111491
**[Test build #57506 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57506/consoleFull)**
for PR 12461 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12832#issuecomment-216109792
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/12832#issuecomment-216109796
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/12832#issuecomment-216109419
**[Test build #57502 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57502/consoleFull)**
for PR 12832 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12831#issuecomment-216108953
**[Test build #57505 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57505/consoleFull)**
for PR 12831 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12833#issuecomment-216108829
Thanks - merging in master / branch-2.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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12833
---
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 dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12831#issuecomment-216108755
PySpark error is irrelevant to this PR. I'll rebase this to retrigger
Jenkins.
---
If your project is set up for it, you can reply to this email and have your
Github user kasjain commented on the pull request:
https://github.com/apache/spark/pull/12356#issuecomment-216108723
Resolved the merge conflicts for easy merging
---
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/12833#issuecomment-216108558
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 benmccann opened a pull request:
https://github.com/apache/spark/pull/12833
Fix reference to external metrics documentation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/benmccann/spark patch-1
Alternatively you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12356#issuecomment-216108200
**[Test build #57504 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57504/consoleFull)**
for PR 12356 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12831#issuecomment-216108047
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/12831#issuecomment-216108046
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/12831#issuecomment-216107981
**[Test build #57503 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57503/consoleFull)**
for PR 12831 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11105#issuecomment-216107872
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/11105#issuecomment-216107874
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/11105#issuecomment-216107383
**[Test build #57494 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57494/consoleFull)**
for PR 11105 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12830#issuecomment-216106479
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/12830#issuecomment-216106483
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/12830#issuecomment-216106407
**[Test build #57501 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57501/consoleFull)**
for PR 12830 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12830#discussion_r61702820
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SparkSession.scala
---
@@ -635,6 +642,122 @@ class SparkSession private(
object SparkSession
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/12820#discussion_r61702404
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -1530,6 +1546,17 @@ object RewritePredicateSubquery
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12830#discussion_r61702208
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SparkSession.scala
---
@@ -635,6 +642,122 @@ class SparkSession private(
object
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12830#issuecomment-216102730
Yes, right. And, this can reduce the `import` statement for `SparkConf` and
`SparkContext` for those people. It become much simpler. Cool. I will update my
PR
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12830#issuecomment-216102470
Yes. Technically we don't really reduce the line length, but definitely
reduces the number of concepts people need to use if they are just using
DataFrame/Dataset.
---
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12830#issuecomment-216102294
Thank you for notifying me. It looks good to me. Then, the three-line
pattern will be replace into one factory statement, right?
**Spark 1.x**
```
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12828#issuecomment-216102318
cc @yhuai
---
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/12828#issuecomment-216102279
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/12828#issuecomment-216102278
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/12828#issuecomment-216102217
**[Test build #57500 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57500/consoleFull)**
for PR 12828 at commit
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/12173#issuecomment-216101785
@falaki okay, fixed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12832#issuecomment-216101694
**[Test build #57502 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57502/consoleFull)**
for PR 12832 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12831#issuecomment-216101693
**[Test build #57503 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57503/consoleFull)**
for PR 12831 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12832#issuecomment-216101460
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 rxin opened a pull request:
https://github.com/apache/spark/pull/12832
[SPARK-15054] Deprecate old accumulator API
## What changes were proposed in this pull request?
This patch deprecates the old accumulator API.
## How was this patch tested?
N/A
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/12831
Fix lint errors on hive module.
## What changes were proposed in this pull request?
This issue fixes or hides 181 Java linter errors introduced by SPARK-14987
which copied hive
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12830#issuecomment-216101059
**[Test build #57501 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57501/consoleFull)**
for PR 12830 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12830#issuecomment-216100989
cc @yhuai @andrewor14
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/12830
[SPARK-15052][SQL] Use builder pattern to create SparkSession
## What changes were proposed in this pull request?
This patch creates a builder pattern for creating SparkSession. The new
code is
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-216099984
cc @liancheng @yhuai It is ready for review. Thanks!
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12801#issuecomment-216099929
cc @rxin It is ready for review. : )
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12774#issuecomment-216099597
cc @yhuai
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12827
---
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12774#issuecomment-216098660
@gatorsmile Does that maybe imply closing this for now and make a JIRA or
send a email to dev-mailing list in order to discuss this further?
---
If your project
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12827#issuecomment-216098578
Merging in master / branch-2.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 does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11919#issuecomment-216097487
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/11919#issuecomment-216097488
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/11919#issuecomment-216097418
**[Test build #57493 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57493/consoleFull)**
for PR 11919 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12173#issuecomment-216097386
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/12268#issuecomment-216097352
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/12173#issuecomment-216097385
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/12268#issuecomment-216097353
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/12173#issuecomment-216097314
**[Test build #57499 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57499/consoleFull)**
for PR 12173 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12827#issuecomment-216097296
**[Test build #2956 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2956/consoleFull)**
for PR 12827 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-216097282
**[Test build #57498 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57498/consoleFull)**
for PR 12268 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12827#issuecomment-216097168
**[Test build #2955 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2955/consoleFull)**
for PR 12827 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12829#issuecomment-216096849
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/12173#issuecomment-216096594
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/12173#issuecomment-216096591
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 abhi951990 opened a pull request:
https://github.com/apache/spark/pull/12829
[SPARK-15045] Update TaskMemoryManager.java
## What changes were proposed in this pull request?
Removed the DeadCode as suggested.
You can merge this pull request into a Git repository
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12173#issuecomment-216096520
**[Test build #57497 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57497/consoleFull)**
for PR 12173 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12774#issuecomment-216096227
IMO, the current behavior is expected. If the document is not clear, we
should correct the document.
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12828#issuecomment-216095931
**[Test build #57500 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57500/consoleFull)**
for PR 12828 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-216095497
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 gatorsmile opened a pull request:
https://github.com/apache/spark/pull/12828
[SPARK-14993] Fix Partition Discovery Inconsistency when Input is a Path to
Parquet File
What changes were proposed in this pull request?
When we load a dataset, if we set the path to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-216095498
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/11724#issuecomment-216095438
**[Test build #57495 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57495/consoleFull)**
for PR 11724 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-216094877
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/12268#issuecomment-216094875
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/12268#issuecomment-216094838
**[Test build #57496 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57496/consoleFull)**
for PR 12268 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12629#issuecomment-216094824
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/12629#issuecomment-216094823
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/12629#issuecomment-216094731
**[Test build #57492 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57492/consoleFull)**
for PR 12629 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12827#issuecomment-216093900
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12817
---
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/12817#issuecomment-216092645
I also created a follow-up ticket for moving the options to function
arguments: https://issues.apache.org/jira/browse/SPARK-15050
---
If your project is set up for
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12817#issuecomment-216092582
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12817#issuecomment-216092409
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/12817#issuecomment-216092410
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/12817#issuecomment-216092342
**[Test build #57491 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57491/consoleFull)**
for PR 12817 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12173#issuecomment-216091524
**[Test build #57499 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57499/consoleFull)**
for PR 12173 at commit
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/12173#discussion_r61697613
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVRelation.scala
---
@@ -74,12 +76,17 @@ object CSVRelation extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-216091185
**[Test build #57498 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57498/consoleFull)**
for PR 12268 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12817#issuecomment-216090703
@rxin I see. Thank you.
---
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/12173#issuecomment-216090645
**[Test build #57497 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57497/consoleFull)**
for PR 12173 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12817#issuecomment-216090565
Don't worry about it. We can just build it on top of this (we should still
document them, just better as function arguments).
---
If your project is set up for it, you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12268#issuecomment-216090185
**[Test build #57496 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57496/consoleFull)**
for PR 12268 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12817#issuecomment-216090207
Sure. Thank you. Do you want me to remove Python documentation here?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12817#issuecomment-216089939
The scala changes lgtm.
One thing I just realized -- for Python, I think we should turn those into
named arguments, rather than just options. Can you do that in a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11724#issuecomment-216089483
**[Test build #57495 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57495/consoleFull)**
for PR 11724 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11105#issuecomment-216089167
**[Test build #57494 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57494/consoleFull)**
for PR 11105 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12827#issuecomment-216089149
**[Test build #2956 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2956/consoleFull)**
for PR 12827 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11919#issuecomment-216089159
**[Test build #57493 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/57493/consoleFull)**
for PR 11919 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12827#issuecomment-216089139
**[Test build #2955 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2955/consoleFull)**
for PR 12827 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12827#issuecomment-216088747
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/11105#issuecomment-216088653
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12827#issuecomment-216088750
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/11919#issuecomment-216088511
Merged with the latest from master (got out of sync) and made the minor CR
changes.
---
If your project is set up for it, you can reply to this email and have your
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/11919#issuecomment-216088321
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
1 - 100 of 263 matches
Mail list logo
