TL;DR: We’re updating how auto-generated email from Github will be
threaded on your mailing lists. If you want to keep the old defaults,
details are below.
We’re pleased to let you know that we’re tweaking the way that auto-
generated email from Github will appear on your mailing lists. This
will
Andy:
I saw two emails from you from yesterday.
See this thread: http://search-hadoop.com/m/JW1q5opRsY1
Cheers
On Fri, Dec 19, 2014 at 12:51 PM, Andy Konwinski
wrote:
> Yesterday, I changed the domain name in the mailing list archive settings
> to remove ".incubator" so mayb
Yesterday, I changed the domain name in the mailing list archive settings
to remove ".incubator" so maybe it'll work now.
However, I also sent two emails about this through the nabble interface (in
this same thread) yesterday and they don't appear to have made it throu
I just changed the domain name in the mailing list archive settings to remove
".incubator" so maybe it'll work now.
Andy
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/Nabble-mailing-list-mirror-errors-This-post-has-NOT-been-accepted
I just changed the domain name in the mailing list archive settings to remove
".incubator" so maybe it'll work now.
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/Nabble-mailing-list-mirror-errors-This-post-has-NOT-been-accepted-by-t
Yeah, it looks like messages that are successfully posted via Nabble end up
on the Apache mailing list, but messages posted directly to Apache aren't
mirrored to Nabble anymore because it's based off the incubator mailing
list. We should fix this so that Nabble posts to / archiv
1560.n3.nabble.com/). However, there
> are many posts in Nabble that are not posted to the Apache lists and are
> flagged with "This post has NOT been accepted by the mailing list yet."
> errors.
>
> I suspect that the issue is that users are not completing the sign-up
> conf
t;This post has NOT been accepted by the mailing list yet."
errors.
I suspect that the issue is that users are not completing the sign-up
confirmation process (
http://apache-spark-user-list.1001560.n3.nabble.com/mailing_list/MailingListOptions.jtp?forum=1),
which is preventing their emails fr
Hi
I'd like to announce a couple of updates to the SparkR project. In order to
facilitate better collaboration for new features and development we have a
new mailing list, issue tracker for SparkR.
- The new JIRA is hosted at https://sparkr.atlassian.net/browse/SPARKR/ and
we have migrate
> The script you're talking about, is it merge_spark_pr.py [1] ?
Yup, that’s it.
>
>> Note by the way that using GitHub is not at all necessary for using Git. We
>> happened to do our development on GitHub before moving to the ASF, and all
>> our developers were used to its interface, so we s
Le 4 mai 2014 à 06:30, Matei Zaharia a écrit :
> Hi Nicolas,
>
> Good catches on these things.
>
>> Your website seems a little bit incomplete. I have found this page [1] with
>> list the two main mailing lists, users and dev. But I see a reference to a
>> mai
Hi Nicolas,
Good catches on these things.
> Your website seems a little bit incomplete. I have found this page [1] with
> list the two main mailing lists, users and dev. But I see a reference to a
> mailing list about "issues" which tracks the sparks issues when it was hos
Hi,
Your website seems a little bit incomplete. I have found this page [1] with
list the two main mailing lists, users and dev. But I see a reference to a
mailing list about "issues" which tracks the sparks issues when it was hosted
at Atlassian. I guess it has moved ? where ?
And is
Hey All,
We've created a new list called revi...@spark.apache.org which will
contain the contents from the github pull requests and comments.
Note that these e-mails will no longer appear on the dev list. Thanks
to Apache Infra for helping us set this up.
To subscribe to this e-mail:
reviews-sub
14 matches
Mail list logo
