From owner-freebsd-current Wed Apr 2 15:20:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA03799 for current-outgoing; Wed, 2 Apr 1997 15:20:28 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA03773; Wed, 2 Apr 1997 15:20:10 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA14842; Wed, 2 Apr 1997 16:02:31 -0700 From: Terry Lambert Message-Id: <199704022302.QAA14842@phaeton.artisoft.com> Subject: Re: ufs lock panic in -current To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 2 Apr 1997 16:02:31 -0700 (MST) Cc: terry@lambert.org, phk@critter.dk.tfs.com, ache@nagual.ru, dyson@FreeBSD.ORG, bde@zeta.org.au, current@FreeBSD.ORG In-Reply-To: <18006.860021091@time.cdrom.com> from "Jordan K. Hubbard" at Apr 2, 97 02:44:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Pretty clearly, I'm going to have to redo them all, now that the > > target has moved. I did this once already for the changes I already > > sent to Julian. > > No, no, just upload them *now* please! Phk is already more than > familiar with the degree of target movement involved, and putting them > up for public display is precisely where you've waffled out on this > issue *every single time* it's come up. If you don't want to release > your bits, fine, but then kindly *stop* talking about how reluctant we > are to integrate them everytime someone so much as gives you an > opening! You can't have it both ways, OK? Please, just take phk up > on his offer and ** upload your changes *** so that we can maybe even > get *past* this "2 year's worth of delay" you keep talking about. > Don't make it 3 years through your own initiative now, eh? :-) And precisely what is wrong with the set of scaled down patches that meet your "not unrelated" criteria which I have submitted, but which you have not yet integrated, either? If it isn't obvious to you by now, I don't trust you to see the intent behind my implementation choices, since you did not see the (obvious to me) relationship between the changes I initially submitted. Since you were unwilling to discuss *why* I made the changes the way I did, and instead simply rejected them without discussion, you should be able to understand why I want to spoon-feed them to you in chunks. I'd rather not have you exercise "editorial license" to remove what you see as "unrelated and useless changes" and what I see as necessary support infrastructure for what I want to do next. That is, I'd rather you didn't prevent me from doing what I want to do next because you aren't willing to spend the time to find out where I'm headed. I am here to work on a platform which provides me the ability to do further research. I am not here to be your code supermarket. I'd rather have no editiorial criticism than destructive editorial criticism, thank you. Giving you the changes incrementally seems to be the only reliable way to achieve this. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.