Date: Sat, 7 Jul 2001 20:13:57 -0500 From: Alfred Perlstein <bright@sneakerz.org> To: David O'Brien <obrien@FreeBSD.org> Cc: Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp>, jhb@FreeBSD.org, current@FreeBSD.org Subject: Re: Lock of struct filedesc, file, pgrp, session and sigio Message-ID: <20010707201357.G88962@sneakerz.org> In-Reply-To: <20010707180112.A20193@dragon.nuxi.com>; from obrien@FreeBSD.org on Sat, Jul 07, 2001 at 06:01:12PM -0700 References: <20010531130155.A58258@dragon.nuxi.com> <200106011228.f51CSvD46848@rina.r.dl.itc.u-tokyo.ac.jp> <20010602125223.J31257@dragon.nuxi.com> <200106040748.f547mUD53783@rina.r.dl.itc.u-tokyo.ac.jp> <200106181004.f5IA4VD63112@rina.r.dl.itc.u-tokyo.ac.jp> <200107020812.f628CfK44241@rina.r.dl.itc.u-tokyo.ac.jp> <20010707164249.C88962@sneakerz.org> <20010707160545.A20360@dragon.nuxi.com> <20010707191128.E88962@sneakerz.org> <20010707180112.A20193@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* David O'Brien <obrien@FreeBSD.org> [010707 20:01] wrote: > On Sat, Jul 07, 2001 at 07:11:28PM -0500, Alfred Perlstein wrote: > > * David O'Brien <obrien@FreeBSD.org> [010707 18:06] wrote: > > > On Sat, Jul 07, 2001 at 04:42:49PM -0500, Alfred Perlstein wrote: > > > > I'm going to be giving this code some testing, not that you have to > > > > wait for me to finish, but it seems like no one has stepped forward > > > > to review this. I'd like to see it committed, so either go ahead > > > > or wait for my review if it makes you more comfortable. > > > > > > Uh.. your "go ahead" attitude is what made the Alpha so damned unstable. > > > We don't need an encore from you. > > > > Piss off david, with everything under giant there's still problems. > > Go blame someone else. > > Ok, then honestly. Tell me what commit made it so unstable. It was very > stable right before your commit and hasn't been since. I am willing to > except that some commit after your exposed some dormant bug if you can > point out the commit. A stock kernel on June 28th couldn't even make it > to single user. I'm not interested in wasting time tracking down bugs for your arch. I agree that there were problems with the vm commit, but with everything back under Giant again, as well as the code recently backed out by Dillon, I really don't see how I could still be causing you any misery. Anyhow, the simple fact is that if you're unable to cope with some instability for a short amount of time you shouldn't be running -current. You should be sticking to -stable. There's a war going on between people trying to get new code into the base and those simplifying/tidying the code. I'm 100% sure it's not malicious, however the fact is that Seigo's patch is horribly broken now because of a lot of minor cleanups, if the massive amount of work he's done is tossed in the trash because he allows his work to get too out of date to ever make it into the base system it would be quite a loss. Finally, if you're so damn concerned about your precious alpha I expect you or at least ANYONE WHO CARES ABOUT ALPHA TO ASSIST IN TESTING THESE DIFFS. thank you very much, -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010707201357.G88962>