Ya, I'll probably unsubscribe if I get broken build emails…  Pls create another 
list.

On 2012-03-31, at 9:46 AM, Ivan Vučica wrote:

> This way, everyone will get a chance to be spammed, and everyone will get a 
> chance to ignore the mail. I don't think you'll get the effect you're aiming 
> for. It's better if just the person who broke the thing got the mail, and if 
> others could occasionally check the build logs to see if anything is broken.
> 
> Frankly, I'd unsubscribe from gnustep-dev (which may come as a relief to some 
> :-)) since my inbox is already too full of various things I want to act upon, 
> but never get a chance to. (Current unread conversation count: 414).
> 
> On Sat, Mar 31, 2012 at 17:12, Gregory Casamento <[email protected]> 
> wrote:
> I, honestly, would like it reported to the list so that people OTHER
> than the person who broke it can act on it.
> 
> All too often people will ignore the email.  If it is sent to the
> list, the maintainers as well as the person who broke it will know
> about it.
> 
> Alternatively I could, instead of putting it to the list, copy myself
> and the other maintainers (Fred, Richard, David, etc) so that they can
> see when and if the build is broken.  But I would rather not spam
> personal emails in that way.
> 
> Later, GC
> 
> On Sat, Mar 31, 2012 at 11:05 AM, Ivan Vučica <[email protected]> wrote:
> > Sending a mail to the person who broke the build really is the best way to
> > go.
> >
> > But please do consider opening at least the logs for viewing purposes, so
> > the person who broke the thing (and other interested parties) can see what
> > went wrong. :-)
> >
> > On Sat, Mar 31, 2012 at 16:48, Gregory Casamento <[email protected]>
> > wrote:
> >>
> >> David,
> >>
> >> If you're asking if I can make Jenkins available on a website which is
> >> accessible to the outside world, I'm not sure if I should until I
> >> configure the logins so that not just everyone can administer it.
> >>
> >> Once I have that set up I will make this public.  Also, I will remove
> >> [email protected], if you guys would like me to make it just send to
> >> the people who broke the build, that's fine.   I did a test with my
> >> own gnu address and it bounced, so I will need to manually configure
> >> the addresses in Jenkins for each of us.
> >>
> >> Thanks, GC
> >>
> >> On Sat, Mar 31, 2012 at 9:50 AM, David Chisnall <[email protected]> wrote:
> >> > On 31 Mar 2012, at 14:48, [email protected] wrote:
> >> >
> >> >> See <http://192.168.1.6:8080/job/gnustep/12/>
> >> >
> >> > If you're going to spam the list with these things, could you at least
> >> > use a publicly routable address?
> >> >
> >> > David
> >> >
> >> > -- Sent from my Difference Engine
> >> >
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Gregory Casamento
> >> Open Logic Corporation, Principal Consultant
> >> yahoo/skype: greg_casamento, aol: gjcasa
> >> (240)274-9630 (Cell)
> >> http://www.gnustep.org
> >> http://heronsperch.blogspot.com
> >>
> >> _______________________________________________
> >> Gnustep-dev mailing list
> >> [email protected]
> >> https://lists.gnu.org/mailman/listinfo/gnustep-dev
> >
> >
> >
> >
> > --
> > Ivan Vučica - [email protected]
> >
> >
> 
> 
> 
> --
> Gregory Casamento
> Open Logic Corporation, Principal Consultant
> yahoo/skype: greg_casamento, aol: gjcasa
> (240)274-9630 (Cell)
> http://www.gnustep.org
> http://heronsperch.blogspot.com
> 
> 
> 
> -- 
> Ivan Vučica - [email protected]
> 
> 
> _______________________________________________
> Gnustep-dev mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/gnustep-dev

_______________________________________________
Gnustep-dev mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/gnustep-dev

Reply via email to