Index

Show enters and exits. Hide enters and exits.

00:01:16duncanmvok, I can do that too
00:02:12brixenthank you
00:14:04duncanmvbrixen: do you need spec/code also separated in the format patch? or you guys take care of doing two commits?
00:20:05brixenduncanmv: they need to be separate commits
00:22:18brixenduncanmv: you can concat them into a single gist to put in the ticket
00:22:26brixengit am is smart enough to deal with that
00:26:32duncanmvuhm, not enough to link the commits from my repo in the ticket?
00:27:32brixenI prefer git fps so I can easily browse, edit, apply etc
00:27:47brixenso, if you link to your commits, your asking me to deal with your repo
00:27:54brixenI refuse to do that with rubyspec
00:28:23brixenevan has been more permissive here, but if you want me to look at your ticket, you increase the odds by making it simple
00:28:33brixenwhich is a gist containing a git fp :)
00:36:49duncanmvuhm, gist does not allow upload
00:36:53duncanmvcopy paste is bad
00:43:25duncanmvbrixen: http://github.com/evanphx/rubinius/issues#issue/446
00:43:30duncanmvbrixen: did not figure how to tag
00:44:31duncanmvCan I run one spec only? spec/ruby/optional/capi/struct_spec.rb ?
00:44:54brixenI use it's all text ff plugin, so I don't need to copy paste http://gist.github.com/554460
00:45:12brixenalso, you copy paste all kinds of things, like terminal output when debugging
00:45:16brixenanyway...
00:45:27brixenbin/mspec spec/ruby/optional/capi/struct_spec.rb
00:45:43brixenadd -tr to run with the ruby exe on your path
00:45:56brixenotherwise, it runs with rbx by default
00:46:02duncanmvno, I want to run with rubinius :-)
00:46:20brixenyou want to run with MRI until you're sure the spec passes ;)
00:47:54brixengotta run, back later...
18:05:24boyscoutUse the specified socket type instead of Socket::AF_UNSPEC, fixes #442 - a4e5958 - Dirkjan Bussink
18:14:31boyscoutCI: rubinius: a4e5958 successful: 3520 files, 15244 examples, 43093 expectations, 0 failures, 0 errors
18:20:20dbussinkevan: ah, understood your comment here wrong then i guess
19:00:55evandbussink: I was just mentioning that other patch as interesting
19:01:00evannot as something we were emulating.