On Thu, Jan 13, 2011 at 16:10, Christopher Sean Morrison <[email protected]> wrote: > > Also, any user-visible changes you make should be documented in the > top-level NEWS file with one-line per change. If it's something a > user can see, however small, it should usually be listed. > > Note that there's a specific format to the lines and it should have a > detailed commit message with what changed, why, and the impact. The > last commit comment is auto-associated with that line and reviewed as > part of configuration control. > > Feel free to ask any questions if they come to mind and aren't > covered by HACKING.
WILCO And thanks again. -Tom ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
