Re: Is anyone still using this list?

Hi Allwyn,

I agree with you that the list should be closed and the project be declared 
unmainstained. The spca50x projecthas had a relatively long and succesfull life, 
but all good things come to an end. Or in this case, the code lives on 
elsewhere, in the spirit of open source :-)

Cheers,
Tomas



> From: Mr Allwyn Fernandes <[email protected]>
> To: SPCA50x Linux Device Driver Development 
><[email protected]>
> Sent: Thu, February 17, 2011 2:36:12 AM
> Subject: [Spca50x-devs] Is anyone still using this list?
> 
> As this list has not seen any traffic in over 6 months, and all development is 

> now being done on the v4l lists, I think my objections to shutting this list 
> down back in 2007 are now irrelevant. 
> 
> Is there anyone who thinks  this list (and/or this sourceforge project in 
> general) should remain open?  Specifically, Michel and Jef, are you still 
> interested in having this  mailing list around?
> 
> If no-one has any objections, I will close this list  on 31 March 2011, and put 
>
> the project into unmaintained  state.
> 
> Thoughts?
> 
> Cheers,
> 
> Allwyn.
> 
> 
> -- 
> Allwyn  Fernandes
> Director
> Stobor Pty  Ltd
> 
> ------------------------------------------------------------------------------
> The  ultimate all-in-one performance toolkit: Intel(R) Parallel Studio  XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix  more than 250 security defects in the development cycle.
> Locate bottlenecks  in serial and parallel code that limit  performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Spca50x-devs  mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/spca50x-devs
> 


      

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb