I don't think it does.
On Fri, Feb 7, 2014 at 8:58 PM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > If we reply these emails, will the reply be posted on pull request > discussion board automatically? > > if yes, that would be very nice > > -- > Nan Zhu > > > > On Friday, February 7, 2014 at 9:23 PM, Henry Saputra wrote: > > > I am with Chris on this one. > > > > These github notifications are similar to JIRA updates that in most > > ASF projects are sent to dev@ list, and these are valid messages that > > contributors in the project should concern about. > > > > Especially the PPMCs (which willl be PMCs hopefully soon) need to know > > about them and become audit trail/ archive of development discussions > > for ASF. > > > > We already have user@ list which targeted for people interested to ask > > for questions using Spark and should be the proper list for people > > interested on using Spark. > > > > As Matei have said, you can filter these github notifications email > easily. > > > > Thanks, > > > > > > - Henry > > > > > > On Fri, Feb 7, 2014 at 6:02 PM, Chris Mattmann <mattm...@apache.org(mailto: > mattm...@apache.org)> wrote: > > > Guys this Github discussion seems like dev discussion in which case it > > > must be > > > on dev list and not moved - the whole point of this is that > development, > > > including > > > conversations related to it, which are the lifeblood of the project > should > > > occur > > > on the ASF mailing lists. > > > > > > Refactoring the lists is one thing for the more automated messages, > but the > > > comments below look like Kay commenting on some relevant stuff in which > > > case > > > I would argue against (paraphrased) "moving it to some ASF list that > those > > > who > > > care can subscribe to". "Those who care" in this case should be people > who > > > care about Kay's comments (which aren't automated commit messages from > > > some bot; > > > they are relevant dev comments) in which case "those who care" should > be > > > the > > > PMC. > > > > > > My suggestion is if there is a notifications list set up, it can be > like > > > for > > > automated stuff - but *NOT* for dev discussion -- that needs to happen > on > > > the > > > dev lists. If it's on another list, then I would expect periodically > > > (frequently; > > > with enough diligence to VOTE on and discuss and contribute to) to see > that > > > flushed or summarized on the dev list. > > > > > > Cheers, > > > Chris > > > > > > > > > > > > > > > -----Original Message----- > > > From: Andrew Ash <and...@andrewash.com (mailto:and...@andrewash.com)> > > > Reply-To: "dev@spark.incubator.apache.org (mailto: > dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org (mailto: > dev@spark.incubator.apache.org)> > > > Date: Friday, February 7, 2014 5:43 PM > > > To: "dev@spark.incubator.apache.org (mailto: > dev@spark.incubator.apache.org)" <dev@spark.incubator.apache.org (mailto: > dev@spark.incubator.apache.org)> > > > Subject: Re: [GitHub] incubator-spark pull request: > > > > > > > +1 on moving this stuff to a separate mailing list. It's Apache > policy > > > > that discussion is archived, but it's not policy that it must be > > > > interleaved with other dev discussion. Let's move it to a > > > > spark-github-discuss list (or a different name) and people who care > to see > > > > it can subscribe. > > > > > > > > > > > > On Fri, Feb 7, 2014 at 5:19 PM, Reynold Xin <r...@databricks.com(mailto: > r...@databricks.com)> wrote: > > > > > > > > > I concur wholeheartedly ... > > > > > > > > > > > > > > > On Fri, Feb 7, 2014 at 4:55 PM, Dean Wampler < > deanwamp...@gmail.com (mailto:deanwamp...@gmail.com)> > > > > > wrote: > > > > > > > > > > > This SPAM is not doing anyone any good. How about another > mailing list > > > > > for > > > > > > people who want to see this? > > > > > > > > > > > > Sent from my rotary phone. > > > > > > > > > > > > > > > > > > > On Feb 7, 2014, at 10:33 AM, mridulm <g...@git.apache.org(mailto: > g...@git.apache.org)> wrote: > > > > > > > > > > > > > > Github user mridulm commented on the pull request: > > > > > > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484468 > > > > > > > > > > > > > > I am hoping that the PR Prashant Sharma submitted would also > > > > > include > > > > > > > ability to check these things once committed ! > > > > > > > Thanks Kay > > > > > > > > > > > > > > > > > > > > > On Sat, Feb 8, 2014 at 12:01 AM, Kay Ousterhout < > > > > > > notificati...@github.com (mailto:notificati...@github.com > )>wrote: > > > > > > > > > > > > > > > I don't know of any precommit scripts (I think there's been > talk of > > > > > > adding > > > > > > > > a general style checker script but AFAIK it hasn't been done > yet); > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I > > > > > > just > > > > > > > > add highlighting in my editor so it's obvious when I'm > writing > > > > > > > > > > > > > > > > > > > > > > > > > > > > > lines > > > > > > that > > > > > > > > are longer than 100 characters. > > > > > > > > > > > > > > > > -- > > > > > > > > Reply to this email directly or view it on GitHub< > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/incubator-spark/pull/517#issuecomment-34484190 > > > > > > > > > > > > > > . > >
