#emc-devel | Logs for 2009-11-02

[17:54:49] <cradek> * cradek is afraid he buried dalegrover with too much information
[17:54:52] <SWPadnos> hmmm. there are a lot more perl warnings/errors when I run the logger script
[17:56:38] <dalegrover> There's a lot to learn about the internal structure.
[17:57:08] <cradek> yeah, there are lots of layers passing messages around
[18:01:41] <JT-Work> should I change the manual to reflect the current behavior of M3/4?
[18:04:40] <dalegrover> Would there be interest (other than myself) in having a session at the CNC Workshop to go over the various layers, modules, etc. that make up EMC2?
[18:04:46] <cradek> ha, that would sure be easier than fixing it
[18:05:16] <cradek> dalegrover: I'd definitely like to attend that
[18:06:33] <cradek> (I'm not sure I'm qualified to run it, though)
[18:08:20] <dalegrover> How does the big picture of EMC2 get passed along? http://www.linuxcnc.org/docview/html//code_Code_Notes.html warns that it is somewhat out of date...
[18:10:08] <cradek> if I know the big picture (and that's not clear) it was learned through trying to fix bugs and add features
[18:10:23] <cradek> and help from others answering my questions of course
[23:51:46] <skunkworks> cradek: did you backport the threading fix - or is it only in master?
[23:52:11] <skunkworks> (I looked thru the git log and didn't see it - although it is the first time I have done that.. :P)
[23:55:38] <jepler> *a* fix is in 2.3.4, but master got an additional fix beyond what is in 2.3.4
[23:56:08] <skunkworks> jepler: thanks