Re: Committing changes to CVS

[Paul <paul.corner-at-tesco.net>]

Hi Jon

Two routes spring to mind - 1) Set up a Sourceforge account and give Will or 
Fred a shout. After you have write access to the CVS repository, download a 
copy, make the changes and then commit them to SF.
2) Download the current CVS sources and make a back up copy. Make your 
changes to the code and then generate a diff file using the back up copy as a 
reference. Post this diff somewhere and invite the developers to test and 
commit on your behalf.

There is a section in the handbook on becoming a developer writen by Ray.

Regards, Paul.


On Saturday 03 Aug 2002 5:32 am, Jon Elson wrote:
> Is there any sort of description on how to get my changes into the
> SourceForge distribution?  Since these changes are quite extensive, there
> probably needs to be some sort of evaluation and testing of these changes,
> to make sure they don't
> break something else.  Others may be quite interested in this, however,
> because it can move ALL auxilliary I/O over to the real-time side.  This
> allows bits of registers to be shared without timing conflict when
> accessing the registers.