From owner-freebsd-current Thu Feb 28 14:43:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by hub.freebsd.org (Postfix) with ESMTP id 6739737B400; Thu, 28 Feb 2002 14:43:20 -0800 (PST) Received: from fwd07.sul.t-online.de by mailout01.sul.t-online.com with smtp id 16gZGd-0008NH-02; Thu, 28 Feb 2002 23:43:15 +0100 Received: from twoflower.liebende.de (320072111332-0001@[217.80.121.170]) by fmrl07.sul.t-online.com with esmtp id 16gZGP-1IbWqGC; Thu, 28 Feb 2002 23:43:01 +0100 Subject: RE: Updated ATAPI/CAM patches From: Jan Stocker To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1014936105.388.17.camel@twoflower> Mime-Version: 1.0 X-Mailer: Evolution/1.0.2 Date: 28 Feb 2002 23:41:51 +0100 X-Sender: 320072111332-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2002-02-28 at 23:15, Julian Elischer wrote: > We have CVS Okay.. thats a piece software.. > Why not commit the prototype now and update it as people get the corner > cases worked out? If Thomas can and will maintain it, ok... else read my comment from my last mail... > The code doesn't interfere with either the CAM system or the ATAPI system > that I can see. So lately atapi_softc disapperead (o.k. has been renamed). So what to do... is the person who made the change responsible to change the affected code (maybe changing this struct causes something more than find/replace the old name) or do you want to wait for the maintainer to fix it and kernel is broken for this time. So you need a person who really want this, have time and the knowledge to do it. You cant check it in and lets see what happens. Jan > > On Thu, 28 Feb 2002, Jan Stocker wrote: > > > I think Thomas is doing here a quite good job and it is also to him to > > decide to include his sources and maybe maintain them. The ata sources have > > changed a lot the last weeks, so until Thomas thinks his sources are under > > heavy development too, both should do their jobs and we've some patches from > > Thomas. If you include it now one depends of the other and you may get into > > the problem of both altering the code from the other at the same time. > > The (somewhat selfish) behavior to include it and give maintainership to > > someone else leads to a originator stopping his work or the creation of 2 > > parallel solutions. Isn't it better the core team (or someone else thinking > > (s)he's a better idea) supports Thomas and a stable and good solution is > > integrated later (maybe with maintainership of Thomas)? > > > > Jan > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message