Re: code submission

[Derek Robert Price]

This is the correct list for patches, but there are a number of things 
you should be aware of:

To be accepted, patches require documentation in doc/cvs.texinfo and 
test cases in src/sanity.sh.
Patches should follow the CVS coding standards.
Patches should be submitted in small, managable chunks, for instance one 
bug fix or feature per patch.
For more information on submitting patches to CVS, please see the 
HACKING and DEVEL-CVS files in the top level of the CVS source.

Submissions to bug-cvs@gnu.org are considered explicit release of the 
content under the GNU GPL.  For more information on the GNU GPL, please 
see the COPYING file in the top level of the CVS source distribution or 
<http://gnu.org>.

Derek

--
               *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
--
Rick:  How long was it we had, honey?
Elsa:  I didn't count the days.
Rick:  Well I did, every one of them.  Mostly I remember the last one.  The wow
      finish.  The guy standing on the station platform in the rain with a
      comical look on his face because his insides had been kicked out.

                - Humphrey Bogart & Ingrid Bergman, _Casablanca_


Samson Chan wrote:

> Hi,
>
>  
>
> I have my changes to the CVS code at my workplace, and I wonder if the 
> changes should be added to the cvs repository.  The changes involve 
> better support for CVS GUI clients.  I am not sure where to start, and 
> this mailing list is used for development discussion.  So do I need to 
> subscribe and become a member?? Can someone give me some directions 
> please?  Thanks.
>
>  
>
>  - Samson
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bug-cvs mailing list
> Bug-cvs@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-cvs
>