Date: Tue, 1 May 2007 04:31:55 -0700 From: Alfred Perlstein <alfred@freebsd.org> To: Andrey Chernov <ache@freebsd.org>, Mark Linimon <linimon@lonesome.com>, Roman Kurakin <rik@inse.ru>, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/sysinstall main.c Message-ID: <20070501113155.GD13868@elvis.mu.org> In-Reply-To: <20070501084514.GA4889@nagual.pp.ru> References: <20070430181824.GA83415@nagual.pp.ru> <20070430225717.GA7008@VARK.MIT.EDU> <20070501000242.GA19510@nagual.pp.ru> <20070501002817.GA887@nagual.pp.ru> <463690FE.9000209@inse.ru> <20070501010709.GA1304@nagual.pp.ru> <20070501013957.GX13868@elvis.mu.org> <20070501064828.GA3836@nagual.pp.ru> <20070501083032.GA9361@soaustin.net> <20070501084514.GA4889@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrey, If the fallout from your changes broke a bunch of things in -current, then we can expect the fallout in -stable to be even worse. Your query about bug reports is a straw man as anticipating a lot of fallout which has already occured does not require that I actually have a bug report. The end result is more users being bitten because a discussion regarding this has obviously not taken place. And yes, you're being a jerk. :) -Alfred * Andrey Chernov <ache@FreeBSD.org> [070501 01:45] wrote: > On Tue, May 01, 2007 at 03:30:32AM -0500, Mark Linimon wrote: > > On Tue, May 01, 2007 at 10:48:28AM +0400, Andrey Chernov wrote: > > > On Mon, Apr 30, 2007 at 06:39:57PM -0700, Alfred Perlstein wrote: > > > > Using the strategy "commit to -current then suffer the fallout" > > > > is pretty bogus. > > > > > > The only possible. Nobody can run all ports at once. Kris already promise > > > all ports build results with those changes in, lets see. > > > > There have been many runs, in the past, with src changes put into the > > cluster and then tested, before the src changes were committed. This is > > the process that is always used to get new versions of gcc into the tree, > > for instance. > > This ones are not such vital as gcc changes which can break all programs > at once, so can't be ever nearly compared with. For what we have --current > for, if every change will go to the cluster first? > > And the question remains: > Is something currently broken _for_you_? I still have no reports. > > -- > http://ache.pp.ru/ -- - Alfred Perlstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070501113155.GD13868>