Index

Show enters and exits. Hide enters and exits.

00:01:24jartz leaves the room.
00:03:34AndrewO enters the room.
00:06:29headius leaves the room.
00:06:58ezmobius leaves the room.
00:06:59headius enters the room.
00:08:04antaresFoobarWidget: hi :)
00:08:15FoobarWidgethello
00:09:16ctennis leaves the room.
00:14:13KirinDave enters the room.
00:14:39ctennis enters the room.
00:17:37rby_ leaves the room.
00:19:28wycats_ leaves the room.
00:26:07rueFoobarWidget: Apache does need help--the terminal kind--but I mainly wanted to pick your brain about the architecture you chose. As it happens, I am just on my way out though
00:26:34rueantares_: Just paste the .pub to pastie and give him the link
00:26:43FoobarWidgetsure just ask
00:30:48rueFoobarWidget: Was the COW/GC behaviour your main focus? My approach is essentially crafting an application server mode into Rubinius itself
00:31:21FoobarWidgetyou're referring to mod_rails/passenger, right?
00:32:00FoobarWidgetcopy-on-write friendliness was an important design goal. but it was also designed to work fine without proper copy-on-write semantics
00:32:06FoobarWidgetthe main focus is ease of deployment
00:32:40headius leaves the room.
00:33:04rueFoobarWidget: Cool. Certainly looks like you met that one
00:33:21FoobarWidgetthanks :)
00:33:47FoobarWidgetother important goals are of course security, stability, low maintenance overhead, easy installation, etc etc
00:33:52headius enters the room.
00:33:58FoobarWidgetand acceptable performance
00:34:00rueFoobarWidget: Was there anything in particular you were running into with MatzRuby? Something that we can address in Rubinius?
00:34:15FoobarWidgetI don't say "fastest" because that's just not possible with apache's architecture
00:34:43FoobarWidgethm, not that I know of. as far as I'm aware rubinius has already addressed (or will address) all the shortcoming in MRI that I see
00:35:07rueHeh. Yes, I am constantly amazed at the Apache "architecture"
00:35:46FoobarWidgetthe prefork MPM is kinda legacy. probably mostly because mod_perl/mod_php and such aren't thread-safe
00:36:14rueHard to say which party is at fault :)
00:36:19FoobarWidgetyeah
00:36:44FoobarWidgethow does your design look like?
00:37:16FoobarWidgetwill it embed rubinius in the apache address space?
00:37:36rueNo, we came to the conclusion early on that it will not be advantageous to anyone
00:37:44FoobarWidgetyeah
00:38:07rueSo we are actually doing a hard split between the adapter and the backend/daemons
00:38:08FoobarWidgetit'll do all kinds of nasty things to you, like running rubinius as root or leak file descriptors
00:38:20rueYep.
00:39:18rueThe idea in the most generic case would be that N backends serve a specific location/dir, M serve another location etc.
00:40:25FoobarWidgetis the ability to be usable on a shared host a goal?
00:40:31rueYep
00:40:51FoobarWidgetwell, then I'm not sure whether that is a good idea. shared hosts usually host thousands of websites on a single server
00:41:01FoobarWidgetif you have to manually specify the number of backends per virtual host,
00:41:05FoobarWidgetthen it quickly becomes a pain
00:41:45FoobarWidgetand depending on the current site traffics, some backends may be wasted because they're idling and doing nothing
00:41:45rueIt would be, definitely. Massive shared hosting will use a slightly different resource pooling model
00:41:51wycats enters the room.
00:41:51FoobarWidgetpassenger has a single backend pool for the entire apache
00:42:09FoobarWidgetand there's a single maximum limit
00:43:40rueYeah, that definitely simplifies handling in a case like that
00:44:13FoobarWidgetthough the pool algorithm is kinda complex
00:44:22FoobarWidgetit tries hard to minimize spawning
00:44:31FoobarWidgetand keeps backend restarts in mind
00:45:48rueYep yep. I am leaning on actually divergent implementations for the three main types of environments
00:46:06FoobarWidgetwhat resource pooling model do you use for massive shared hosting?
00:46:09rueOf course from the sysadmin side it should all be equally simple to configure and so on
00:46:21FoobarWidgetyes
00:47:02FoobarWidgetwe've clearly documented our algorithm, in readable pseudo code, including invariant descriptions and thread-safety notes
00:47:04rueIt requires a bit more on the adapter side, though
00:47:06FoobarWidgetso you may want to take a look at it once it's released :)
00:47:11rueFoobarWidget: Definitely
00:47:25antares_ leaves the room.
00:47:57antares_ enters the room.
00:48:43rueI have not settled on anything at this point although I have done some preliminary testing. Mainly I have been concentrating on the non-massive hosting side first
00:50:56headius leaves the room.
00:51:34FoobarWidgethow do you plan to test your massive shared hosting resource pooling model?
00:56:05wycats leaves the room.
00:57:44rueHeh, that part should be interesting. Simulations can only go so far.
00:58:13FoobarWidgetapache modules are also a pain to debug
00:58:28FoobarWidgethard to tell what they're doing
00:58:34rueHonestly, though, I am not that ambitious for the first cut. I want to see how the backend side comes into being mainly
00:58:51rueYeah, it is abysmal. Even Apache::Test merely scratches the surface
00:59:19FoobarWidgetso you'd have to rely on log files
01:00:14FoobarWidgetpassenger has integration tests which test the apache module
01:00:24FoobarWidgetit does so by creating a custom apache config file
01:00:31FoobarWidgetwhich contains a few stub websites
01:00:36ruePossibly to some degree, yeah. I am setting up integration/functional tests with mocked requests and backend
01:00:41FoobarWidgetand then telling the system's apache to use that config file
01:00:49FoobarWidgetthen it sends http requests and checks the results
01:00:52rueHeh, pretty much the same there.
01:01:16rueI am also abusing C a bit to be able to get some sembalance of unit tests in place
01:01:20FoobarWidgetand I've made 90% of the code apache-independent
01:01:28FoobarWidgetso that I can test them independently
01:01:36rueDefinitely helps
01:01:38FoobarWidgetthat's so much easier than restarting apache over and over
01:01:49FoobarWidgetand it allows me to use valgrind
01:03:42rueYups. I have been a bit cross whether to push a lot of logic in the adapter or not
01:04:29FoobarWidgetthe apache-independent approach has the added benefit that it can be ported to other web servers (say, nginx or lighttpd) relatively easily
01:04:38KirinDave leaves the room.
01:06:03headius enters the room.
01:06:47rueNow, you are still referring to code that is a part of the adapter?
01:08:13rueOr do you actually have a three-tier with the adapter, the "middleware" and then the backend?
01:12:35imajes enters the room.
01:13:42imajes_ leaves the room.
01:16:38headiusevenin
01:16:45rueAlohaloo
01:19:05jrun leaves the room.
01:27:05eventualbuddha leaves the room.
01:33:56antaresheadius, evening
01:34:07headiushiya hiya!
01:40:48FoobarWidgetrue: I guess you could call it "middleware"
01:41:02FoobarWidgetthough I think the word "middleware" is a buzzword :)
01:41:24FoobarWidgetit's just a bunch of classes that are part of the apache module, but can be compiled without apache
01:41:38FoobarWidgetand parts are written in ruby
01:48:47jrun enters the room.
01:53:20imajes_ enters the room.
02:06:03macournoyer leaves the room.
02:08:13octopod leaves the room.
02:09:40_VVSiz_ enters the room.
02:09:50FoobarWidgetgotta sleep now
02:09:51FoobarWidgetbye
02:10:16antaresFoobarWidget: bb
02:10:16MenTaLguY enters the room.
02:10:28rueFoobarWidget: Later! Sorry, in and out
02:10:32rueMeh :P
02:14:57dkubb enters the room.
02:18:21wycats enters the room.
02:22:28ezmobius enters the room.
02:25:59benburkert_ enters the room.
02:27:21benburkert leaves the room.
02:27:53VVSiz_ leaves the room.
02:31:25jan_andersson enters the room.
02:46:03jan_andersson leaves the room.
02:46:29wycats leaves the room.
03:01:26benburkert enters the room.
03:01:26benburkert_ leaves the room.
03:01:30wycats enters the room.
03:02:00chop3 leaves the room.
03:02:33imajes leaves the room.
03:05:06imajes enters the room.
03:08:46antaresrue, a question
03:09:32antaresrue: you mentioned my docpatch to shotgun still have some redundant comments. Could you point me to them? I want to do a cleanup.
03:15:42jayWHY enters the room.
03:16:00jayWHY leaves the room.
03:20:27squeegy leaves the room.
03:25:23rubuildius_amd64 leaves the room.
03:26:13lachie enters the room.
03:27:17wycats leaves the room.
03:29:09jrun leaves the room.
03:33:09djwhittevan: are you saying I just need to remove *.d files to get the parallel make working?
03:36:58squeegy enters the room.
03:43:27rueantares_: Function name is `baker_gc_set_forwarding_address`, comment is `/* sets forwarding pointer on object */`
03:49:22antaresrue, it was going to describe how forwarding pointer is used, I will remove it for now
04:03:09rubuildius_amd64 enters the room.
04:03:54djwhittthere's going to be a duplicate run for rubuildius_amd64
04:04:07djwhittfeel free to ignore it
04:07:03jicksta leaves the room.
04:12:16ko1_away leaves the room.
04:13:14mediogre enters the room.
04:13:30rueantares_: You can leave it out or fix it, however you want to do it
04:19:49antares_ leaves the room.
04:29:29ko1_away enters the room.
04:30:30elight enters the room.
04:36:34womble enters the room.
04:53:29jptix_ enters the room.
04:53:46jptix_ leaves the room.
04:54:39obiejuan enters the room.
05:11:25obiejuan leaves the room.
05:11:28lachie leaves the room.
05:33:43srbaker leaves the room.
05:33:51imajes_ leaves the room.
05:36:45dewd_ leaves the room.
05:37:11srbaker enters the room.
05:37:11benburkert leaves the room.
05:37:29benburkert enters the room.
05:40:07AndrewO leaves the room.
05:42:08jptix_ enters the room.
05:45:52elight enters the room.
05:48:17jptix_ leaves the room.
05:56:03jptix leaves the room.
05:58:04mae leaves the room.
05:58:05mae_ enters the room.
06:00:16rubuildius_amd64Charles Comstock: 5caf94ce6; 1764 files, 6137 examples, 20403 expectations, 0 failures, 0 errors; http://rafb.net/p/Vq2amJ79.html
06:03:39elight leaves the room.
06:07:23RyanTM leaves the room.
06:12:43srbaker leaves the room.
06:23:12jartz enters the room.
06:32:51mae_ leaves the room.
06:32:57mae enters the room.
06:39:29mae leaves the room.
06:52:19headius_ enters the room.
06:55:25jptix enters the room.
07:04:40headius_ leaves the room.
07:05:11jptix leaves the room.
07:05:41headius leaves the room.
07:11:56qwert666 enters the room.
07:21:42qwert666_ enters the room.
07:37:17qwert666 leaves the room.
07:52:17jinjing enters the room.
08:01:01hassox enters the room.
08:01:10hassox leaves the room.
08:06:37ezmobius leaves the room.
08:07:03lachie enters the room.
08:25:36hassox enters the room.
08:26:18hassox leaves the room.
08:28:31ezmobius enters the room.
08:33:11jartz leaves the room.
08:33:15jartz enters the room.
08:53:24GMFlash leaves the room.
08:53:30GMFlash enters the room.
08:57:41lachie leaves the room.
09:08:10ezmobius leaves the room.
09:11:40lachie enters the room.
09:19:27GMFlash leaves the room.
09:37:03lachie leaves the room.
09:48:24thehcdreamer enters the room.
10:00:21brainopia enters the room.
10:15:50brainopia leaves the room.
10:16:15brainopia enters the room.
10:18:39brainopia leaves the room.
10:25:38lachie enters the room.
10:32:16jptix enters the room.
10:42:49rby enters the room.
11:02:51antares enters the room.
11:32:19jan_andersson enters the room.
11:34:00lachie leaves the room.
11:48:38chris2 enters the room.
12:06:29mae enters the room.
12:10:40maehello my intrepid rubinius warriors
12:17:11jptix leaves the room.
12:52:32jrun enters the room.
13:03:21VVSiz_ enters the room.
13:05:22nemerle leaves the room.
13:15:01jartz leaves the room.
13:16:00cored enters the room.
13:21:33_VVSiz_ leaves the room.
13:26:33AndrewO enters the room.
13:43:27antares leaves the room.
13:44:22antare1 enters the room.
13:53:01srbaker enters the room.
13:54:51srbaker leaves the room.
14:01:36jrun leaves the room.
14:03:28mutle enters the room.
14:03:42RyanTM enters the room.
14:03:50jinjing_ enters the room.
14:03:52jinjing leaves the room.
14:05:57srbaker enters the room.
14:13:15enebo enters the room.
14:13:57jrun_ enters the room.
14:15:21bigl enters the room.
14:18:36benburkert leaves the room.
14:21:11jrun enters the room.
14:21:11jrun_ leaves the room.
14:25:15cored leaves the room.
14:32:04enebo leaves the room.
14:33:53chop3 enters the room.
14:33:54jrun leaves the room.
14:34:03jrun enters the room.
14:37:53dancroak enters the room.
14:39:52thehcdreamer leaves the room.
14:52:06binary42 enters the room.
14:56:16jrun_ enters the room.
14:56:16jrun leaves the room.
15:00:42GMFlash enters the room.
15:01:54dewd enters the room.
15:02:54jrun_ leaves the room.
15:06:02jrun enters the room.
15:08:19Skip enters the room.
15:10:54benburkert enters the room.
15:25:03brainopia enters the room.
15:30:28rby leaves the room.
15:44:45fbuilesv leaves the room.
15:45:01fbuilesv enters the room.
15:46:49jrun leaves the room.
15:49:52rubuildius_amd64 leaves the room.
16:00:13AndrewO leaves the room.
16:04:48jinjing enters the room.
16:07:41mediogre leaves the room.
16:12:19jptix enters the room.
16:15:04Skip leaves the room.
16:18:16jinjing_ leaves the room.
16:19:13jinjing_ enters the room.
16:20:21mediogre enters the room.
16:24:47joachimm enters the room.
16:26:41brainopia leaves the room.
16:27:47chop3 leaves the room.
16:33:01jinjing leaves the room.
16:34:01jinjing enters the room.
16:35:19Skip enters the room.
16:48:35AndrewO enters the room.
16:49:33jinjing_ leaves the room.
16:50:30RyanTM leaves the room.
16:54:46mediogre leaves the room.
17:11:39obiejuan enters the room.
17:20:26jartz enters the room.
17:21:47dewd leaves the room.
17:23:14wycats enters the room.
17:28:24wycats leaves the room.
17:30:34chris2 leaves the room.
17:31:29headius enters the room.
17:34:52benburkert_ enters the room.
17:36:16jptix leaves the room.
17:37:01cyndis leaves the room.
17:37:12dctanner enters the room.
17:37:29cyndis enters the room.
17:51:16obiejuan leaves the room.
17:57:24benburkert leaves the room.
17:58:24thehcdreamer enters the room.
17:59:57rueMorgenstrom
18:01:58rueFinal draft, it looks like: https://www.securecoding.cert.org/confluence/display/seccode/CERT+Secure+Coding+Standards
18:03:37djwhittneeto
18:04:55djwhittor neato depending on how much you care about spelling
18:05:29rueCould be a security issue
18:05:53djwhittso, what's everyone up to these days. I keep expecting to see some hug commit that fix everything
18:06:28djwhitt*huge
18:06:29headiuseverything!
18:06:34djwhittman, can't type
18:06:51benburkert_ leaves the room.
18:07:56headiusdjwhitt: well, what are you up to? committed anything lately?
18:08:19djwhittheh, well, I just got rubuildius to quit sending duplicate messages after restarts
18:08:22djwhittthat's something
18:08:45djwhittother than that not really though :)
18:10:15rueThe argument eval order will be a fairly big one, I suspect
18:11:08mae_ enters the room.
18:11:14headiusyeah I would imagine
18:11:23headiustouches a lot of code
18:11:38headiusand a tough one to avoid some amount of perf degradation
18:12:00mae leaves the room.
18:27:26brainopia enters the room.
18:35:24headius leaves the room.
18:35:50headius enters the room.
18:35:56tizianobis enters the room.
18:41:49rueStill not sure why we are changing it but nevertheless :)
18:41:53benburkert enters the room.
18:44:26antare1rue: hi there :)
18:45:08rueAhlo
18:55:38headiusrue: because it's wrong the way it is
18:55:43headiusoh wait
18:55:47headiuswhat are we talking about? :)
18:58:58rby enters the room.
19:00:22binary42 leaves the room.
19:01:59rueheadius: Argument evaluation order (which should be unspecified)
19:02:11rueI dunno if there was another problem in the same area
19:02:29headiuswell, you can argue that all you want, but it's not unspecified in ruby
19:02:29headiusif shit breaks, it's broken
19:02:40headiuslanguage idealism aside
19:05:58headiusit's also not unspecified in java
19:06:00headiusso it's certainly not the norm
19:08:00tizianobis leaves the room.
19:11:39FoobarWidget enters the room.
19:12:54rueheadius: It most definitely is unspecified. I am not arguing that people have--incorrectly--relied on a specific order.
19:17:39rueFoobarWidget: *wave* Dashing off again, thanks for the answer last night. That is basically what I was asking, you do not really have three "physical" units of code, the adapter side is just logically split in two
19:18:12FoobarWidgethi rue
19:18:22headiusI don't think matz would agree
19:18:26FoobarWidgetyeah, it's a logical split. I actually have about 20 source files
19:18:49headiushe said something along the lines of "I think evaluation order must be left to right" on ruby-core...which is as close as we'll get to specified behavior
19:19:14headiusat any rate it's hard to argue that it's unspecified when there's no spec
19:19:20headiusMRI is the spec and MRI evaluates left-to-right
19:19:29headiusso the specified behavior is left-to-right
19:19:40FoobarWidgetrue: btw, I'm wondering how you want to handle misbehaving apps
19:19:53FoobarWidgetsuppose an app does "while true; sleep(1); end"
19:19:56FoobarWidgetwhat happens?
19:21:14tarcieridoesn't see what else could happen but the ostensible
19:21:35tarcierithe loop ticks once a second?
19:21:46FoobarWidgetno I mean, what will mod_rubinius do about it
19:22:08FoobarWidgetyou obviously don't want a single app to lock up apache
19:22:43tarcieriwas under the impression mod_rubinius would be backed by multiple worker VMs
19:23:25FoobarWidgetyeah. but what if an attacker continuously accesses a website that runs "while true; something; end"?
19:23:40FoobarWidgetall the worker VMs will be busy trying to run infinite loops
19:23:44tarcieria configurable request timeout would be a good idea
19:24:24rueHm, it should not lock -Apache- up. That backend process obviously would be, but I am not sure it is my place to say how it needs to be handled. I think a default max execution time and a timeout policy should be reasonable
19:24:35tarcieriyes
19:25:02FoobarWidgeta timeout is the most obvious solution, yes. but if the attacker is continuously accessing a broken website, then all the backend processes will be locked up for at least the duration of the timeout
19:25:05rueBut that is more for the server admin to decide in their individual case given the suitable tools to do so of course
19:25:06headiusFoobarWidget: if that were the case I probably wouldn't deploy that code :)
19:25:12FoobarWidgetleaving very little time for normal ruby websites to be processed
19:25:28FoobarWidgetwell I'm trying to think from the point of view of a shared host :)
19:25:46tarcieriFoobarWidget: the same can be said for an attacker who is able to create long-running SQL queries
19:25:57rueI think that breaks the distinction between what is the server admin's responsibility
19:26:05FoobarWidgetyeah, I suppose so
19:26:10rueWhile we can help him out, ultimately the sysadmin needs to set the policy
19:26:28ruePlus there are lots of anti (D)DoS tools and even modules there
19:27:01headiusare there any specs for left-to-right? I feel like writing some
19:27:23GMFlash leaves the room.
19:27:34rueFoobarWidget: So we can probably say that X seconds is the max execution time by default, Y for request timeout. Most installations do not need to change them but they can be if needed
19:27:52FoobarWidget>> def foo(a, b); end
19:27:52FoobarWidget=> nil
19:27:52FoobarWidget>> foo(puts("a"), puts("b"))
19:27:52FoobarWidgeta
19:27:52FoobarWidgetb
19:28:06tarcieria side effect other than puts is probably in order
19:28:12FoobarWidgetright-to-left? my ruby interpreter says things are evaluated left to right
19:28:12tarcierilike assignment
19:28:58tarcieri>> (a = 1) + (a = 2)
19:29:08headiusa = [1, 2]; foo(a.pop, a.pop)
19:29:15tarcieria.should == 2
19:29:38headiusI've written some eval order tests for jruby in the past
19:29:49headiusI can make some new specs
19:30:32rueheadius: I will see what the new Ruby Language book says
19:32:18anon enters the room.
19:34:11anony enters the room.
19:36:25Fishy5 enters the room.
19:37:19dewd enters the room.
19:39:01headiuswell here's an interesting surprise
19:39:09headiusruby evaluates a block pass before its arguments
19:46:03headiusugh, and before receiver
19:46:07headiusthat's unexpected :)
19:46:43headiusI'd argue that's an unexpected bug
19:46:56headiusit doesn't fit with l-to-r argument ordering
19:46:57anonuser leaves the room.
19:48:46Fishy5Evaluating a block shouldn't be able to change any state anyways, so I don't see that it would matter being out of order.
19:49:08headiusfoo(a += 1, a += 1, &(a += 1; proc {}))
19:49:18headiusor any method that returns a proc, for that matter
19:49:28thehcdreamer leaves the room.
19:49:31headiusit will be called before arguments or receiver are evaluated
19:49:42headiusthat's a spicy meatball
19:51:11jartz leaves the room.
19:51:43boyscout1 commit by Charles Oliver Nutter
19:51:44boyscout * Added order-of-evaluation spec and tags for rubinius failures.; 7d18171
19:51:46anon leaves the room.
19:52:05lvmc enters the room.
19:52:36headiusjruby fails the two that order block pass in odd ways
19:57:29ctennis leaves the room.
20:02:22Fishy5Aye. I guess that could be bad. :\
20:05:28brainopia leaves the room.
20:05:51rubuildius_ppcCharles Oliver Nutter: 7d181716a; 1765 files, 6142 examples, 20435 expectations, 0 failures, 0 errors; http://pastie.caboo.se/paste/169171
20:07:28anony leaves the room.
20:09:30jayWHY enters the room.
20:12:59anonuser enters the room.
20:20:08dysinger enters the room.
20:29:58jartz enters the room.
20:35:44headiusI emailed ruby-core about the block pass ordering
20:35:58headiusgoofy as hell
20:40:05wifelette enters the room.
20:41:53wmoxam leaves the room.
20:50:24lvmc leaves the room.
20:52:24wmoxam enters the room.
20:54:41wycats enters the room.
21:12:59wycats leaves the room.
21:13:13rubuildius_amd64 enters the room.
21:22:38rubuildius_amd64Charles Oliver Nutter: 7d181716a; 1765 files, 6139 examples, 20406 expectations, 0 failures, 0 errors; http://rafb.net/p/Qf2dHO22.html
21:24:30FoobarWidgetin an interview with evan, I've heard that you guys have a subversion mirror for your git repo
21:24:33FoobarWidgetis it still online?
21:47:10ezmobius enters the room.
21:48:03srbaker leaves the room.
21:48:06srbaker_ enters the room.
21:51:49aotearoa enters the room.
21:52:24jayWHY leaves the room.
21:57:19headiusFoobarWidget: no, they abandoned the svn mirror a long time ago
21:57:49FoobarWidgetwhy's that?
21:57:56Ski1 enters the room.
22:01:58headiusI guess it was too buggy
22:02:46scooprheadius, interesting stuff on duby!
22:02:58headiusahh thanks
22:03:09headiushadn't posted an update in a couple weeks, and been doing a lot of work on it
22:03:26headiushopefully this weekend I'll try to wire up a JVM bytecode backend to test it all out from end to end
22:03:29headiusbbiab
22:03:58scooprthat'd be rather awesome
22:05:58wmoxam leaves the room.
22:11:39Skip leaves the room.
22:13:52jptix enters the room.
22:21:30srbaker_ leaves the room.
22:21:40srbaker enters the room.
22:23:05binary42 enters the room.
22:32:41jartz leaves the room.
22:33:34fbuilesvHi, I'm writing a spec for REXML, so far I've done the document class and you can see it in http://tinyurl.com/28nwc2 . Any comments/suggestions will be appreciated.
22:40:03GMFlash enters the room.
22:40:18antare1rue: I am yet to meet Evan online to give him my pubkey pastie, so here is another shotgun doc patch: http://tinyurl.com/29zb25
22:40:40wmoxam enters the room.
22:45:20KirinDave enters the room.
22:55:47jptix_ enters the room.
23:01:59_mutle enters the room.
23:05:34MenTaLguY enters the room.
23:07:24AndrewO leaves the room.
23:09:45FoobarWidget leaves the room.
23:12:02jayWHY enters the room.
23:15:55macournoyer enters the room.
23:17:46mutle leaves the room.
23:25:25cremesantare1: just send him a note here including the reference to your commit and a pastie link; he'll likely see if when he reads the logs
23:29:12antare1cremes_: will do
23:30:11dysinger leaves the room.
23:30:55KirinDave leaves the room.
23:31:00antare1evan: commit ref: http://git.rubini.us/?p=code;a=commit;h=55cbcc60f2c3804c62d5d73ff06ebbc4c0b00b95, here is my public key: http://pastie.org/private/t0pffcnbg1gtsdfaaf5ng -- may I have a commit bit, please? :)
23:35:34antare1 leaves the room.
23:38:20macournoyer leaves the room.
23:38:59macournoyer enters the room.
23:42:31bigl leaves the room.
23:43:28qwert666_ leaves the room.
23:44:10antares enters the room.
23:45:32jicksta enters the room.
23:48:04MenTaLguY leaves the room.
23:48:08wycats enters the room.
23:48:12Jicksta leaves the room.
23:48:16jicksta enters the room.
23:55:38srbaker leaves the room.
23:57:58antareshttp://tinyurl.com/2q8cp6 example group could use before block probably