www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Lindner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-2885) subversion commit emails going to incorrect email (shindig-dev@shindig.apache.org)
Date Tue, 20 Jul 2010 01:31:51 GMT

    [ https://issues.apache.org/jira/browse/INFRA-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890123#action_12890123

Paul Lindner commented on INFRA-2885:

Hey Paul:

In responding to this, I noticed that commit mails are being sent to shindig-dev@shindig.apache.org,
which bounces. I assume I'm getting these b/c commits@ is on there. Assuming we want dev@
to get the mails, we should probably reconfigure. Any idea where that is?


---------- Forwarded message ----------
From: Mail Delivery Subsystem <MAILER-DAEMON@google.com>
Date: Mon, Jul 19, 2010 at 7:57 AM
Subject: Returned mail: see transcript for details
To: fargo@google.com

The original message was received at Mon, 19 Jul 2010 07:56:45 -0700
from kpbe18.cbf.corp.google.com []

  ----- The following addresses had permanent fatal errors -----
   (reason: 550 mail to shindig-dev@shindig.apache.org not accepted here)

  ----- Transcript of session follows -----
... while talking to mx1.eu.apache.org.:
>>> DATA
<<< 550 mail to shindig-dev@shindig.apache.org not accepted here
550 5.1.1 <shindig-dev@shindig.apache.org>... User unknown
<<< 503 RCPT first

Final-Recipient: RFC822; shindig-dev@shindig.apache.org
Action: failed
Status: 5.1.1
Remote-MTA: DNS; mx1.eu.apache.org
Diagnostic-Code: SMTP; 550 mail to shindig-dev@shindig.apache.org not accepted here
Last-Attempt-Date: Mon, 19 Jul 2010 07:56:46 -0700

---------- Forwarded message ----------
From: John Hjelmstad <fargo@google.com>
To: shindig-dev@shindig.apache.org
Date: Mon, 19 Jul 2010 07:56:41 -0700
Subject: Re: svn commit: r965499 - in /shindig/trunk/features: ./ src/main/javascript/features/core.config/
While not quite relevant yet to deployed use cases, what's our thinking on how these flags
will affect behavior at such time as it's possible for a gadget to be a container? Eg. <Require
feature="shindig.container"/>, enabling nested gadgets.

In this case, anything that's acting in a gadget context should register osapi.services. I'm
sure there will be more ambiguity to navigate than just these flags, but did want to point
out one downstream impact.


> subversion commit emails going to incorrect email (shindig-dev@shindig.apache.org)
> ----------------------------------------------------------------------------------
>                 Key: INFRA-2885
>                 URL: https://issues.apache.org/jira/browse/INFRA-2885
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Paul Lindner
>            Assignee: Gavin
> Shindig commit messages are being sent to shindig-dev@shindig.apache.org -- this should
be dev@shindig.apache.org
> Thanks!

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message