On 07/08/2013 07:50 PM, Jon Elson wrote: > Now, I have to get the docs to follow these updates (and also to bring > them up to > date on a lot of other matters, as well.) Are we keeping separate docs that > are in sync with the release versions, and should I treat commits there > the same > as commits to the code? (I know the doc files in master get rebuilt > periodically, > is the same true for the branches?)
The official docs at http://linuxcnc.org/docs has release-specific docs from 2.5 back through 2.0(!), plus master. We treat docs the same as code in this regard: we build it all the time, release it along with the programs, etc. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
