00:14:48  * AtumTquit (Remote host closed the connection)
01:07:27  * qardjoined
01:39:53  * qardquit (Quit: qard)
08:48:23  * joocain2quit (Ping timeout: 255 seconds)
08:50:36  * joocain2joined
11:25:11  * mylesborinsquit (Quit: farewell for now)
11:25:42  * mylesborinsjoined
13:27:18  * AtumTjoined
13:36:27  * listenmorequit (Remote host closed the connection)
13:36:55  * listenmorejoined
15:16:54  * listenmorequit (Remote host closed the connection)
15:17:23  * listenmorejoined
17:28:36  * jasonkjoined
17:30:18  <jasonk>hi all, n00b question -- can the eventloop be "moved" to different threads? What I mean by that is, I create an uv_loop_t via malloc(), do some setup work in one thread (via uv_run(Once)) and transfer that evenloop to a new thread which then carries out further work. This seems to be a easier way to compose tests, for example, but I don't know if its legit
18:39:55  * listenmorequit (Remote host closed the connection)
18:40:22  * listenmorejoined
21:01:43  * listenmorequit (Remote host closed the connection)
21:02:14  * listenmorejoined
21:19:29  * listenmorequit (Remote host closed the connection)
21:20:06  * listenmorejoined
21:34:08  * listenmorequit (Remote host closed the connection)
21:34:39  * listenmorejoined
22:22:14  * listenmorequit (Remote host closed the connection)
22:22:46  * listenmorejoined
23:17:43  * qardjoined
23:44:55  * jasonkquit (Quit: Page closed)
23:45:25  * qardquit (Quit: qard)