[00:08] *** azakai has joined #jsmess
[02:28] *** logchfoo0 starts logging #jsmess at Fri Sep 28 02:28:59 2018
[02:28] *** logchfoo0 has joined #jsmess
[02:49] *** zino has quit IRC (Excess Flood)
[02:52] *** zino has joined #jsmess
[03:10] *** decay has quit IRC (Read error: Operation timed out)
[04:32] *** pfalleno1 has quit IRC (Ping timeout: 268 seconds)
[10:06] *** datajerk has quit IRC (Max SendQ exceeded)
[10:06] *** datajerk has joined #jsmess
[14:00] <SketchCow> OK!
[15:56] <SketchCow> The big event is Wednesday, gotta start locking down
[15:56] <SketchCow> Monday or so, if stuff isn't screenshot, it'll probably be put into a holding pen and worked on and pushed over as it is shot
[16:41] *** godane has quit IRC (Read error: Operation timed out)
[16:48] <Sgeo_> What does locking down imply in terms of new Emularity and vice builds?
[16:48] <Sgeo_> I have the day off today. Was intending to go to NYC but that didn't happen
[17:24] *** godane has joined #jsmess
[19:14] <SketchCow> As of this moment, https://archive.org/search.php?query=emulator%3Avice-resid
[19:14] <SketchCow> 9,643 items that I conisder in good shape
[19:14] <SketchCow> Locking down means I'm making something I can announce that night and in the blog entry and it'll have flaws but not flaws we've already fixed
[20:22] <Sgeo_> Should I go ahead with fixing up the Emularity changes or should I hold off until after Wednesday?
[20:22] <Sgeo_> I am vaguely worried that too long a break will cause me to get bored and wander off for an indeterminate amount of time
[20:38] <db48x> no, we should fix whatever we can before then
[21:52] <SketchCow> No no, keep working
[21:52] <SketchCow> We just always have a backout plan
[22:19] *** azakai has quit IRC (Remote host closed the connection)
[22:20] *** azakai has joined #jsmess