From owner-freebsd-current Thu May 13 0:51:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from moss.nibb.ac.jp (moss.nibb.ac.jp [133.48.46.64]) by hub.freebsd.org (Postfix) with ESMTP id DD83314D5B for ; Thu, 13 May 1999 00:51:12 -0700 (PDT) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (localhost [127.0.0.1]) by moss.nibb.ac.jp (8.8.8/8.8.8) with ESMTP id QAA02437; Thu, 13 May 1999 16:50:59 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: jkh@zippy.cdrom.com Cc: soda@sra.co.jp, dfr@nlsystems.com, current@FreeBSD.ORG Cc: tomoaki@biol.s.u-tokyo.ac.jp Subject: Re: cvs commit: src/sys/pci pcisupport.c From: Tomoaki NISHIYAMA In-Reply-To: <67065.926554325@zippy.cdrom.com> References: <67065.926554325@zippy.cdrom.com> X-Mailer: Mew version 1.94b8 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990513165059Z.tomoaki@moss.nibb.ac.jp> Date: Thu, 13 May 1999 16:50:59 +0900 X-Dispatcher: imput version 990212(IM106) Lines: 38 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Jordan K. Hubbard" Subject: Re: cvs commit: src/sys/pci pcisupport.c Date: Wed, 12 May 1999 17:12:05 -0700 Message-ID: <67065.926554325@zippy.cdrom.com> jkh> I have seen a lot of arguing about technical merits and decisions made jkh> by the core team, but I have yet to see any constructive comments jkh> about fixing the communication problems which led to this decision. I think the best way to fix the communication problem is to discuss on the technical merits, to understand what you think and to make you understand what we think. If the explanation of the code is too short ask questions what is not understood. jkh> Evaluating technology is a jkh> question of deciding which code is both superior AND has the best jkh> longevity, longevity being a more difficult equation which combines jkh> the history of the developers involved and how effective your jkh> communications with them are. In this case, I don't believe jkh> communications are effective and that kills newconfig just as jkh> thoroughly as having the code be a total mess; I think I've pointed jkh> this out several times now. Yes, longevity is an important thing. But it is not only the matter of communication, but it depends on the fundamental design, and on what principle the code is written. Once you understand the fundamental design and the principle it is based on, you will be able to develop them further. Thus we want you understand the design and principle of newconfig, through the code and discussion. You can decide to merge them after understanding the principle. It's not a good idea to reject something without understanding, as to merge something without understanding. -------- Tomoaki Nishiyama e-mail:tomoaki@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message