[DEVELOPERS] Commits

Karolin Seeger ks at sernet.de
Thu Oct 23 12:54:10 GMT 2008


Hey folks,

there are a few rules developers should follow when checking in new
patches. 

1. PLEASE USE SENSIBLE COMMIT MESSAGES!
   Metze already wrote mails about this topic, but some people do still
   ignore the hints.
   The first line should include a _short_ description explaining what the
   patch fixes/changes. If the patch fixes an existing bug, please
   include the bug number (but not only the bug number ;-). 

2. Please do not check trivial patches like whitespace cleanups into the
   production branch (currently v3-2-test).

3. If you check in patches into the production branch, make sure that you
   did test them thouroughly. They must fix a bug and the commit message
   must include a coherent description of the bug fixed.


Karolin

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.SerNet.DE, mailto: Info @ SerNet.DE



More information about the samba-technical mailing list