linux-mips-fnet
[Top] [All Lists]

Re: Work [was: Re: SNI Alliance Partner]

To: linux-mips@fnet.fr
Subject: Re: Work [was: Re: SNI Alliance Partner]
From: "Paolo Bevilacqua" <pab@uni.net>
Date: Mon, 20 Nov 1995 17:30:48 +0100
In-reply-to: Andreas Busse <andy@soft-n-hard.de> "Re: Work [was: Re: SNI Alliance Partner]" (Nov 20, 3:54pm)
References: <199511201454.PAA06588@newton.soft-n-hard.de>
On Nov 20,  3:54pm, Andreas Busse wrote:
> ...
>
> But back to the original problem: I really want to see a realistic
> chance for getting a SNI box to the same state as the Jazz boxes,
> and within a certain time. This is not only a question of "who takes
> care of this baby", it's also a question of the general rules here.
> I know that it isn't fun, but I believe that we need to definitely
> assign project parts to people. The way it worked (or not worked)
> until now is a no-go.
> I don't want to decide about who's doing what, so I ask before:
> Could you all please summarize what you feel responsible for?
> Or, if this needs to be decided first, come to a decision?
>
> The way is should work is that I don't need to ask around to find
> out who's doing what. Everyone should know whom to send patches if
> he's changing something.
> Also, just hoping that someone else will fix or write this and
> that don't work. If you think something needs to be written (such
> as scsi driver), either do it yourself or bother people until
> someone is willing to do it for you. Never just sit down and dream
> of it. It won't come.
>

Ok. This is what i'd like to do, subjected to manage a fix for my low res
board:
- completation of the fast console driver
- SCSI driver

        /pab


<Prev in Thread] Current Thread [Next in Thread>