Date: Mon, 12 Jan 1998 17:59:38 -0800 (PST) From: Tom <tom@uniserve.com> To: Mike Smith <mike@smith.net.au> Cc: shimon@simon-shapiro.org, thyerm@camtech.net.au, current@freebsd.org, Studded@dal.net, kong@kkk.ml.org, Alex Nash <nash@mcs.net> Subject: Re: Commit Approval (was Re: Firewall in kernel? - Found it! ) Message-ID: <Pine.BSF.3.96.980112174611.22477f-100000@shell.uniserve.com> In-Reply-To: <199801130139.MAA04391@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Jan 1998, Mike Smith wrote: > > > > Commonsense? Prohibition? Who knows... I don't understand why some > > > > developers are forced to make changes on branches, while others check > > > > stuff into the mainline branch? > > > > > > Politics. Personal motivation. Percieved scope. > > > > The first. > > All three, at various times, actually. Please be very careful judging > situations based on less than the complete set of facts, and remember > to take into account the entire situation. 8) I take into account only what I read. I've been chastised for doing this before, but it is the only information I have. Perhaps if "core" meeting minutes, or any other kind of "core" publication was made available, people could see more clearly where things are heading. You gave me three choices. As the developer in question said something about the "powers that be" made the decision, I doubt that the last two choices fit, leaving only the first. Doesn't preclude a fourth possibility though. I should clarified my original comment, because "politics" doesn't seem accurate to me either, but I assumed that you were refering to the same unnamed project that I was. ... > In addition to this, the administrative overhead would be not > inconsiderable. The burden on developers that need to deal with build problems in other parts of the tree is also considerable. I believe this is what prompted Simon's to start this thread. Simon is working a kernel based distribued lock manager. I don't think anyone here fails to see the value of this project. But when current is having so many problems it tends to stymie all other projects, other than the one that happens to be destablizing current. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ > > > > Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980112174611.22477f-100000>