On Saturday 31 January 2009 18:43:27 Dave Newton wrote:
>
> This appears to have worked, or at least I haven't received a
> Yahoo-is-sad msg yet.
>
> Dave
>
I'm trying to test it now... It didn't come through to commits@, so I tried to
configure it to send directly to directly to me, and no messa
Wendy Smoak wrote:
On Sat, Jan 31, 2009 at 1:03 PM, Dave Newton wrote:
:
192.87.106.230 does not like recipient.
I think it should be commits (with an s)...
http://mail-archives.apache.org/mod_mbox/struts-commits/
This appears to have worked, or at least I haven't received a
Yahoo-is-sad m
On Sat, Jan 31, 2009 at 1:03 PM, Dave Newton wrote:
> :
> 192.87.106.230 does not like recipient.
> Remote host said: 550 mail to
> commit-allow-subscribe-hudson=hudson.zones.apache@struts.apache.org not
> accepted here
> Giving up on 192.87.106.230.
I think it should be commits (with an s)..
Wes Wannemacher wrote:
On Friday 30 January 2009 09:41:26 Dave Newton wrote:
Wes Wannemacher wrote:
Dave, if you can allow Hudson to send messages to dev@, then I'd be
satisfied. I don't know who originally filed the JIRA on infra...
I have no idea how to do that; all I know how to do is hit "
Sent an empty msg to addr; let me know if it works.
Dave
Wes Wannemacher wrote:
On Friday 30 January 2009 09:41:26 Dave Newton wrote:
Wes Wannemacher wrote:
Dave, if you can allow Hudson to send messages to dev@, then I'd be
satisfied. I don't know who originally filed the JIRA on infra...
I
On Friday 30 January 2009 22:32:42 Don Brown wrote:
> +1
>
> On Sat, Jan 31, 2009 at 2:31 PM, Wendy Smoak wrote:
> > We currently have build status notifications going to commits@ -- I'd
> > prefer to keep the automated messages going there (or to a new
> > notifications@ list) and reserve dev@ fo
+1
On Sat, Jan 31, 2009 at 2:31 PM, Wendy Smoak wrote:
>
> We currently have build status notifications going to commits@ -- I'd
> prefer to keep the automated messages going there (or to a new
> notifications@ list) and reserve dev@ for human conversations. :)
>
> --
> Wendy
>
>
On Thu, Jan 29, 2009 at 8:36 PM, Wes Wannemacher wrote:
> Dave, if you can allow Hudson to send messages to dev@, then I'd be satisfied.
> I don't know who originally filed the JIRA on infra...
We currently have build status notifications going to commits@ -- I'd
prefer to keep the automated mes
On Friday 30 January 2009 09:41:26 Dave Newton wrote:
> Wes Wannemacher wrote:
> > Dave, if you can allow Hudson to send messages to dev@, then I'd be
> > satisfied. I don't know who originally filed the JIRA on infra...
>
> I have no idea how to do that; all I know how to do is hit "accept" and
>
Wes Wannemacher wrote:
Dave, if you can allow Hudson to send messages to dev@, then I'd be satisfied.
I don't know who originally filed the JIRA on infra...
I have no idea how to do that; all I know how to do is hit "accept" and
"deny" links in the emails, and I haven't seen any from Hudson ye
On Thursday 29 January 2009 22:16:30 Dave Newton wrote:
> Wes Wannemacher wrote:
> > Whether we do commits@ or dev@, it doesn't matter to me, I'll leave that
> > up to the group. IIUC, the issue is probably lack of mod access for any
> > of the active devs.
>
> FWIW, I'm been modding this entire co
gmail smtp vs ezmlm - I added myself to the allow and changed my smtp
server :)
- Brett
On 30/01/2009, at 2:16 PM, Dave Newton wrote:
Wes Wannemacher wrote:
Whether we do commits@ or dev@, it doesn't matter to me, I'll leave
that up to the group. IIUC, the issue is probably lack of mod
a
Wes Wannemacher wrote:
Whether we do commits@ or dev@, it doesn't matter to me, I'll leave that up to
the group. IIUC, the issue is probably lack of mod access for any of the
active devs.
FWIW, I'm been modding this entire conversation--for some reason they're
all coming as needing moderatio
On 30/01/2009, at 1:25 PM, Wes Wannemacher wrote:
I kind of figured, but thought it couldn't hurt to try. Brett, can
you look in
and see who is configured as a mod for dev@ commits@, etc. ? I think
the
problem we've had in the past is that the current set of mods have
been too
busy with
On Thursday 29 January 2009 20:31:40 Brett Porter wrote:
> >
> > I sent a blank message to
> >
> > dev-allow-subscribe-hudson=hudson.zones.apache@struts.apache.org
> >
> > but didn't hear anything back from ezmlm... Do I need mod
> > permissions or
> > something?
>
> Yes, you would (otherwise a
On 30/01/2009, at 11:47 AM, Wes Wannemacher wrote:
On Thursday 29 January 2009 19:08:59 Brett Porter wrote:
Hi folks,
This issues was raised with infrastructure last year as Bamboo
couldn't post to comm...@struts. With the changes to use Hudson, is
it
still needed, or are you able to post
On Thursday 29 January 2009 19:08:59 Brett Porter wrote:
> Hi folks,
>
> This issues was raised with infrastructure last year as Bamboo
> couldn't post to comm...@struts. With the changes to use Hudson, is it
> still needed, or are you able to post your notifications now?
>
> - Brett
>
I sent a bl
On Thursday 29 January 2009 19:08:59 Brett Porter wrote:
> Hi folks,
>
> This issues was raised with infrastructure last year as Bamboo
> couldn't post to comm...@struts. With the changes to use Hudson, is it
> still needed, or are you able to post your notifications now?
>
> - Brett
>
> --
> Brett
Hi folks,
This issues was raised with infrastructure last year as Bamboo
couldn't post to comm...@struts. With the changes to use Hudson, is it
still needed, or are you able to post your notifications now?
- Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
19 matches
Mail list logo
