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
> 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.
> 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 [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-scsi" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message