Re: [brlcad-devel] oed: Command and Documentation

[Christopher S. M. <br...@ma...>]

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.

Cheers!
Sean


On Jan 13, 2011, at 4:48 PM, Christopher Sean Morrison wrote:

> On Jan 7, 2011, at 11:32 AM, Tom Browder wrote:
>
>> For scripting it looks like one needs to use B or e command before
>> doing oed.  It's obvious when doing it manually, but it wasn't so
>> obvious when I used the null graphics interface.
>>
>> I've made an attempt at tweaking the oed article and man page xml
>> sources to reflect that and have attached the diff.
>>
>> Best,
>>
>> -Tom
>
> Tom,
>
> You can apply this patch directly yourself.  You were granted commit
> access a while back after you provided a few other useful patches. ;-)
> Just run "svn commit doc/docbook" and it should prompt you for a
> username/password the first time around.  Be sure to read HACKING
> about developer responsibilities if you haven't already and welcome
> to BRL-CAD development!
>
> Cheers!
> Sean
>
>
> ---------------------------------------------------------------------- 
> --------
> 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
> brl...@li...
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel