#linuxcnc-devel | Logs for 2015-10-24

Back
[01:21:42] <KGB-linuxcnc> 03Sebastian Kuzminsky 05v2.4_branch 4a5dda1 06linuxcnc 10(12 files in 6 dirs) g81 test: add repeat cycles * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=4a5dda1
[01:31:43] <KGB-linuxcnc> 03Sebastian Kuzminsky 05v2.5_branch eb911e2 06linuxcnc 10(6 files in 6 dirs) Merge remote-tracking branch 'origin/v2.4_branch' into v2.5_branch * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=eb911e2
[01:31:43] <KGB-linuxcnc> 03Sebastian Kuzminsky 05v2.5_branch 42f6752 06linuxcnc 10src/emc/rs274ngc/interp_cycles.cc interp: comment the "rapid up to R if needed" code * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=42f6752
[01:31:43] <KGB-linuxcnc> 03Sebastian Kuzminsky 05v2.5_branch 1d363f1 06linuxcnc 10src/emc/rs274ngc/interp_internal.hh interp: fix an old bug in canned cycle preliminary & in-between moves * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=1d363f1
[01:36:06] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 61d6c88 06linuxcnc 10src/emc/rs274ngc/interp_cycles.cc 10src/emc/rs274ngc/interp_internal.hh Merge remote-tracking branch 'origin/v2.5_branch' into 2.6 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=61d6c88
[01:36:29] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 3ef729c 06linuxcnc 10src/emc/rs274ngc/interp_internal.hh Merge remote-tracking branch 'origin/2.6' into 2.7 * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3ef729c
[01:36:48] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master 9c15d39 06linuxcnc Merge remote-tracking branch 'origin/2.7' * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9c15d39
[02:09:44] <linuxcnc-build_> build #2875 of 4003.deb-lucid-i386 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4003.deb-lucid-i386/builds/2875 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[02:27:48] <linuxcnc-build_> build #1431 of 4002.deb-hardy-amd64 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4002.deb-hardy-amd64/builds/1431 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[02:30:20] <linuxcnc-build_> build #1431 of 4001.deb-hardy-i386 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4001.deb-hardy-i386/builds/1431 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[02:31:05] <linuxcnc-build_> build #1434 of 4000.deb-hardy-rtai-i386 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4000.deb-hardy-rtai-i386/builds/1434 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[02:33:21] <linuxcnc-build_> build #2874 of 4004.deb-lucid-amd64 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4004.deb-lucid-amd64/builds/2874 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[02:36:17] <linuxcnc-build_> build #2869 of 4006.deb-lucid-rtai-i386 is complete: Failure [4failed shell_3 shell_4] Build details are at http://buildbot.linuxcnc.org/buildbot/builders/4006.deb-lucid-rtai-i386/builds/2869 blamelist: Sebastian Kuzminsky <seb@highlab.com>
[10:15:35] <seb_kuzminsky> all of those failures are our 2.4 debs not passing lintian, which is fine and expected
[10:42:54] <skunkworks> jepler: is your hope to use your streaming work to move rasterizing to a mesa card?
[10:53:18] <jepler> skunkworks: yes
[10:53:43] <jepler> userspace will keep the streaming buffer full, mesa driver will keep a hardware fifo full
[10:54:00] <jepler> new stuff will be needed in the driver too, I think
[10:54:05] <jepler> in the fpga that is
[11:46:39] <jepler> jthornton: is there a better way than a sticky post to announce the forum upgrade date?
[11:47:32] <JT-Shop> let me look
[11:48:42] <JT-Shop> I'd say change the header to reflect the change date, as soon as you pick one I'll change it
[11:48:44] <jepler> also do you know if there's a way to make it all all read-only when I start the upgrade? or is the only option to fully disable it?
[11:49:11] <skunkworks> jepler: cool!
[11:49:13] <JT-Shop> I'd have to look a see
[11:49:55] <JT-Shop> just the forum is being changed?
[11:50:11] <jepler> jthornton: right
[11:50:30] <jepler> changing the rest of the website will come later .. hopefully not very much later
[11:52:16] <JT-Shop> the only option I see is to disable the forum
[11:53:07] <JT-Shop> oh I can lock the forums
[11:53:54] <JT-Shop> like LinuxCNC Announcements is locked and only admin can post to it
[11:54:02] <JT-Shop> so read only yes I can
[11:58:12] <JT-Shop> be back later
[12:32:19] <jepler> ok
[17:17:38] <andypugh> Are other folks being spammed by someone claiming to be Jack Caots?
[17:18:24] <mozmck> yes, they are coming in on the emc-users list
[17:18:58] <mozmck> maybe he has a virus
[17:19:17] <andypugh> They probably don’t even come from him
[19:55:58] <zeeshan> the mach attack
[23:34:33] <skunksleep> Hmmm loop speed? http://www.machsupport.com/forum/index.php/topic,31111.0.html
[23:34:56] <skunksleep> How does that work in windows?