For the record, Paul was given the opportunity to get access to the
new repository -- the same way anyone else gets access.  Sure likes
his FUD, doesn't he?

Message from Chris Radek, April 2006:
> On Tue, Apr 04, 2006 at 10:42:46AM +0100, paul_c wrote:
> > 
> > 
> > If it is the intention of the board to alienate developers and
> restrict 
> > access of the code to a handful of the "in crowd", you will
> succeed.
> 
> Hi Paul, this is of course not the intention.  The code is as
> open as ever at
> 
> http://cvs.linuxcnc.org/cgi-bin/cvsweb.cgi/
> 
> and all the old committers will have commit access as soon as
> they send their public keys as I asked on the devel list.  I have
> not seen any other negative responses to the announcement of this
> move; the sourceforge cvs reliability was unacceptable.
> 
> Chris

Mark

--- paul_c <[EMAIL PROTECTED]> wrote:

> On Wednesday 02 May 2007 17:07, Stephen Wille Padnos wrote:
> > Paul - do you know of any way to use the kernel firmware
> infrastructure
> > to load different firmware sets into multiple cards?
> 
> Stephen - If/when you get elected to the "board" and succeed in
> restoring the 
> CVS repository at Sourceforge where we ALL can have access, I'll
> show you how 
> to handle firmware. Even with bit flipping and assorted sanity
> checks, it 
> would amount to less than 250 lines of code with the added bonus
> of being 
> portable across architectures and relatively immune to on going
> changes to 
> the PCI subsystem within the kernel.
> 
> 
> Regards, Paul.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to