On Fri, Mar 26, 2010 at 07:39:49PM -0700, Stanislav Sedov wrote: > On Fri, 26 Mar 2010 18:34:39 -0500 > Mark Linimon <lini...@lonesome.com> mentioned: > > > On Fri, Mar 26, 2010 at 06:39:51PM +0545, Gabor Kovesdan wrote: > > > It would be nice to receive a failure notification about such things. I > > > didn't get anything neither for this one nor for the previous one. These > > > notifications worked before and there were no commits like this without > > > notifying the maintainer. > > > > I guess I've erred on the side of not notifying people about breakages on > > systems that we don't have tinderboxen for, just to avoid filling up > > people's mailboxes. What do other people think? Am I making a mistake? > > > > (Yes, in a perfect world we have tinderboxen for these ...) > > > > I think it's right thing to do for now. Most people don't have any resources > to fix/test these, and it's not a tier1 platform, so I don't think it make > much sense to bother people with these failures. > Also, it requires a lot of effort to keep track of these failures, which have had a message sent, how long ago, and if more than x days without reply or commit, mark it broken. Given those are Tier-2 platforms and the low frequency of errors, I would say that portmgr can use their time better on other matters.
-erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the future er...@freebsd.org
pgp99Kft5U5df.pgp
Description: PGP signature
