Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/76#issuecomment-36719524
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/75#issuecomment-36719526
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/76#issuecomment-36719525
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13001/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/75#issuecomment-36719527
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13002/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-36719546
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 epahomov opened a pull request:
https://github.com/apache/spark/pull/81
[SPARK-1174] Adding port configuration for HttpFileServer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/epahomov/spark SPARK-1174
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36723648
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/81#issuecomment-36723643
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/82#issuecomment-36723641
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/80#issuecomment-36723647
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/18#issuecomment-36723654
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/18#issuecomment-36728451
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/18#issuecomment-36728453
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13004/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36728450
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36728452
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13003/
---
If your
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36729592
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-36732961
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/80#issuecomment-36732960
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/80#issuecomment-36737006
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36747331
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/34#issuecomment-36747330
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 jyotiska opened a pull request:
https://github.com/apache/spark/pull/83
Fixed link for latest pyspark api guide
Fixed link for PySpark API in Python programming guide to the latest
version.
You can merge this pull request into a Git repository by running:
$ git
Hi, all
Just for curiosity, I grep the source code in core component yesterday, and
found that there are about 30 configuration parameters being used but
undocumented
I have been reading the source code and writing documents for them, nearly
finished…
But I would like to ask before I made
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36753067
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13006/
---
If your project
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-36755664
Thanks Sean.
Multi-class classification and feature importances are important features
that will be added soon. We implemented a minimal feature set since we
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/83#issuecomment-36760892
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/83#issuecomment-36760894
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13007/
---
If your project
Hi David,
Few questions on breeze solvers:
1. I feel the right place of adding useful things from RISO LBFGS (based on
Professor Nocedal's fortran code) will be breeze. It will involve stress
testing breeze LBFGS on large sparse datasets and contributing fixes to
existing breeze LBFGS with the
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/33#issuecomment-36764964
yes I haven't made that change yet. I should have a patch up in a few hours
with that changed. I'm just doing some finally testing on it. I'm changing it
to pass the
On Wed, Mar 5, 2014 at 8:50 AM, Debasish Das debasish.da...@gmail.comwrote:
Hi David,
Few questions on breeze solvers:
1. I feel the right place of adding useful things from RISO LBFGS (based on
Professor Nocedal's fortran code) will be breeze. It will involve stress
testing breeze LBFGS
Tom,
I tried the command line you used and it didn't work for me.
On Fri, Feb 28, 2014 at 6:05 AM, Tom Graves tgraves...@yahoo.com wrote:
what build command are you using?What do you mean when you say YARN
branch?
The yarn builds have been working fine for me with maven. Build command
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/33#issuecomment-36781865
filed https://spark-project.atlassian.net/browse/SPARK-1191
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/83#discussion_r10317227
--- Diff: docs/python-programming-guide.md ---
@@ -146,7 +146,7 @@ sc = SparkContext(conf = conf)
# API Docs
-[API
Hi David,
On Tue, Mar 4, 2014 at 8:13 PM, dlwh david.lw.h...@gmail.com wrote:
I'm happy to help fix any problems. I've verified at points that the
implementation gives the exact same sequence of iterates for a few different
functions (with a particular line search) as the c port of lbfgs. So
On Wed, Mar 5, 2014 at 1:57 PM, DB Tsai dbt...@alpinenow.com wrote:
Hi David,
On Tue, Mar 4, 2014 at 8:13 PM, dlwh david.lw.h...@gmail.com wrote:
I'm happy to help fix any problems. I've verified at points that the
implementation gives the exact same sequence of iterates for a few
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/63#issuecomment-36799644
This looks good -- I've merged this into 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
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/63#issuecomment-36800228
@kayousterhout Thank you very much!
---
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 berngp opened a pull request:
https://github.com/apache/spark/pull/84
[SPARK-1186] : Enrich the Spark Shell to support additional arguments.
Enrich the Spark Shell functionality to support the following options.
```
Usage: spark-shell [OPTIONS]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36811873
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36811871
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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/84#issuecomment-36811862
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 CodingCat opened a pull request:
https://github.com/apache/spark/pull/85
SPARK-1192: The document for most of the parameters used in core component
I grep the code in core component, I found that around 30 parameters in the
implementation is actually used but
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36812172
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 sryza opened a pull request:
https://github.com/apache/spark/pull/86
SPARK-1126. spark-app preliminary
This is a starting version of the spark-app script for running compiled
binaries against Spark. It still needs tests and some polish. The only
testing I've done so
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36812678
I said it is WIP, because of 2 things
1. The document is surely need to be revised, I'm not sure if I understand
all details correctly, though I spent not so
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/70#issuecomment-36812734
Thanks, merged.
---
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36813427
@pwendell , yep, I asked in the mail list, but didn't get response, so I
decided to put the things here first and revise it (e.g. remove those
unnecessary) based on the
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/78#issuecomment-36813430
Hey actually I'll just add this comment in the merge. I'll merge this into
master and 0.9 now.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36815476
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13009/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36815474
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36815535
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/42#issuecomment-36815549
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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36815759
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/42#issuecomment-36815803
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 this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/78
---
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 etrain commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-36817253
This PR is the result of several iterations on the idea of wanting to build
fast decision trees for Spark.
To offer a little more color on the design here, the key
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36818653
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13012/
---
If your
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10330438
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkAppArguments.scala ---
@@ -0,0 +1,155 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user jyotiska commented on a diff in the pull request:
https://github.com/apache/spark/pull/83#discussion_r10330490
--- Diff: docs/python-programming-guide.md ---
@@ -146,7 +146,7 @@ sc = SparkContext(conf = conf)
# API Docs
-[API
GitHub user anitatailor opened a pull request:
https://github.com/apache/spark/pull/87
Example for cassandra CQL read/write from spark
Cassandra read/write using CqlPagingInputFormat/CqlOutputFormat
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/87#issuecomment-36821530
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/33#issuecomment-36821538
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/33#issuecomment-36821651
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13013/
---
If your
GitHub user rezazadeh opened a pull request:
https://github.com/apache/spark/pull/88
Sparkpca
# Principal Component Analysis
Computes the top k principal component coefficients for the m-by-n data
matrix X. Rows of X correspond to observations and columns correspond to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/88#issuecomment-36821826
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/33#issuecomment-36821650
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-36821926
Looks like test failed because of git problems. Retesting later.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10330672
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkAppArguments.scala ---
@@ -0,0 +1,155 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user rezazadeh commented on the pull request:
https://github.com/apache/spark/pull/88#issuecomment-36822139
@mengxr @mateiz All comments from previous PR done, please take a look.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
I did not. They would be nice to have.
On Wed, Mar 5, 2014 at 5:21 PM, Debasish Das debasish.da...@gmail.comwrote:
David,
There used to be standard BFGS testcases in Professor Nocedal's
package...did you stress test the solver with them ?
If not I will shoot him an email for them.
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10330871
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkApp.scala ---
@@ -0,0 +1,178 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
GitHub user puravaggarwal opened a pull request:
https://github.com/apache/spark/pull/89
MetadataCleaner - fine control cleanup documentation
Documentation with reference to commit
b5025d90bbf3e81701a3c3f5e22efbb2e2164eea by Mridul
Date: Fri Oct 4 21:57:57 2013 +0530
-
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10331089
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkApp.scala ---
@@ -0,0 +1,178 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/88#issuecomment-36824070
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36824087
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/89#issuecomment-36824083
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/88#issuecomment-36824072
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13014/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36824086
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 a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10331562
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkAppArguments.scala ---
@@ -0,0 +1,155 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/87#issuecomment-36825120
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/87#discussion_r10331715
--- Diff:
examples/src/main/scala/org/apache/spark/examples/CassandraCQLTest.scala ---
@@ -0,0 +1,124 @@
+/*
+ * Licensed to the Apache Software
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/12#issuecomment-36825497
any further comments?
---
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/33#issuecomment-36825493
Pass securityManager and SparkConf around where we can. Note the changes
to JettyUtils and calling functions. Switch to use SparkConf for getting and
setting configs
Github user jyotiska commented on the pull request:
https://github.com/apache/spark/pull/34#issuecomment-36825757
@mateiz @JoshRosen Can you verify 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36826227
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13015/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36826226
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/91#issuecomment-36826285
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/90#issuecomment-36826288
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/33#issuecomment-36826306
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/33#issuecomment-36826305
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/87#issuecomment-36826290
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 a diff in the pull request:
https://github.com/apache/spark/pull/90#discussion_r10332066
--- Diff: core/pom.xml ---
@@ -269,6 +269,37 @@
/environmentVariables
/configuration
/plugin
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/85#issuecomment-36826295
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/90#discussion_r10332070
--- Diff: core/pom.xml ---
@@ -269,6 +269,37 @@
/environmentVariables
/configuration
/plugin
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/87#issuecomment-36826359
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/90#discussion_r10332109
--- Diff: graphx/pom.xml ---
@@ -70,6 +70,10 @@
artifactIdscalacheck_${scala.binary.version}/artifactId
scopetest/scope
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/33#issuecomment-36826678
@pwendell Ok this should now be 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/90#issuecomment-36827214
Hey @sryza I have a question here. If we shade like this for the `package`
target of core, then as far as I understand this will embed a shaded version of
`asm` inside of
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/90#issuecomment-36827278
@sryza or maybe if we shade _both_ kryo and asm in the package jar, the
shader plug-in is good enough to figure out that one is a dependency of the
other and embed both
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/90#issuecomment-36827609
Oy, good point. Ok, I'll try that out.
---
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
1 - 100 of 118 matches
Mail list logo
