[00:22]  * Nafai installs LightDM
[08:01] <MacSlow> good morning folks
[08:07] <oSoMoN> good morning
[08:07] <andyrock> oSoMoN, good morning
[08:08] <oSoMoN> hey andyrock
[09:00] <Andy80> hi :)
[10:18] <Andy80> nerochiaro: good morning! :) I sent you the patch yesterday :P
[10:20] <nerochiaro> Andy80: great ! i'm not sure if i will review it myself or someone else, but thanks
[10:20] <nerochiaro> Andy80: i will have a look later or monday
[10:23] <Andy80> nerochiaro: thanks :) I also created the "schema" file for the other bug you assigned me, but it's not in patch form... it's just the .schemas file attached to the bug... I neither know if it's ok or not.
[10:25] <nerochiaro> Andy80: Well, it needs to be put somewhere in the package i assume, so do a bzr add of the file in the right place and then push the branch somewhere and ask for a merge review of that branch
[10:28] <Andy80> nerochiaro: I wanted to do it but I really don't know where to put the file... for that reason I simply attached it to the bug ;) p.s: how does it work with bazaar branches exactly? Do I have to always work on the same branch or is it better if I create a new branch for every bug/feature I work on until they're not merged in the main one?
[10:34] <nerochiaro> Andy80: one for every bug. the way it works is that you do a "bzr branch lp:unity-2d workbugxxxx" then you go into the branch and do your work, and commit as often as you like, always with clear commit messages. Push your branch somewhere in lp under your account like lp:~andreagrandi/unity-2d/meaningful_name_for_branch . push often so your work is safe. and once in a while do a "bzr pull" or a "bzr merge lp:unity-2d" to pull in the
[10:34] <nerochiaro> latest changes (and resolve any conflicts). finally when you're done, submit a merge request for the branch. do this for each different bug you work on.
[10:34] <nerochiaro> that's what I do at least :)
[11:04] <daker> good morning
[11:04] <daker> on Unity i have an area where  i can't scroll/click on it is, anyone experiencing the same issue ?
[11:08] <andyrock> daker, the window invisible issue...
[11:08] <andyrock> daker, i think...
[11:09] <daker> bug # ?
[11:09] <andyrock> daker, just a moment
[11:10] <andyrock> daker, look here https://bugs.launchpad.net/unity/+bug/755459
[11:10] <andyrock> daker, i don't know if it is your same bug
[11:10] <daker> ok lemme read the comments
[11:11] <daker> andyrock, yes the same bug ツ
[11:12] <andyrock> daker, quoting Jason: «It's a feature!» :)
[11:16] <daker> thanks andyrock
[11:16] <andyrock> daker, yw ;)
[11:30] <Andy80> nerochiaro: thanks! Sorry for the delay I was away from keyboard :)
[11:30] <nerochiaro> Andy80: no problem
[15:04] <andyrock> hi all
[15:04] <andyrock> i've some `design` problem with this bug
[15:04] <andyrock> https://bugs.launchpad.net/unity/+bug/735031
[15:05] <andyrock> if someone can help me, i will be really happy
[15:09] <andyrock> the problem is: if we drag the launcher with the right click, the quicklist is shown and the drag start
[15:10] <andyrock> why? because the quicklist is shown not only at the down event
[15:10] <andyrock> and not to the click event
[15:11] <andyrock> there are different solutions
[15:11] <andyrock> for example show the quicklist at the click event (not down event)
[15:11] <andyrock> or
[15:12] <andyrock> close the quicklist when drag start
[15:12] <andyrock> BUT we have to show the quicklist after a timeout in this case
[15:59] <njpatel> andyrock, quicklist _should_ be shown on button down (most context menus are)
[15:59] <njpatel> andyrock, maybe when we detect a drag, we just close the active quicklits?
[15:59] <njpatel> quicklist*
[16:00] <andyrock> njpatel, yes... but we have to add a short timeout
[16:00] <andyrock> njpatel, otherwise we have a flash effect!
[16:00] <njpatel> andyrock, why?
[16:00] <njpatel> aah
[16:01] <andyrock> njpatel, quicklist open and close create a flash effect
[16:01] <njpatel> andyrock, I think short timeout is fine, just put a comment in why your doing it like that instead of just closing it straight away
[16:01] <saamm> is it possible that invisible window problem is related to this bug -- Bug #761252
[16:01] <njpatel> saamm, the dash, in natty, is not using an xwindow at all anymore, so it shouldn't be the issue
[16:02] <saamm> oh ok
[16:03] <andyrock> njpatel, ok thx
[16:35] <artfwo> njpatel, about that merge request for bug 728598
[16:36] <artfwo> that was indeed fixed long ago
[16:42] <njpatel> artfwo, awesome, thanks
[16:42] <njpatel> artfwo, could you mark it as super-seeded?
[16:42] <njpatel> or un merge-request
[16:43] <njpatel> (please :)
[16:43] <artfwo> njpatel, how to do this?
[16:43] <sbte> hey, anyone here knows a better place to report this bug? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/785233
[16:43] <sbte> it has a testcase and it's a regression, so it should be easy to fix
[16:45] <artfwo> njpatel, done, deleted the branch entirely, looks like the merge proposal is gone
[16:45] <njpatel> artfwo, I think if you go to the merge page (https://code.launchpad.net/~artfwo/unity/fix-for-728598/+merge/52523) it should have a yellow button that yo ucan click to change the details
[16:45] <njpatel> artfwo, ah, thanks :)
[16:45] <njpatel> cdbs, ping
[16:46] <jcastro> njpatel: might be good to do a call for "hey everyone, unpropose your old crap"
[16:46] <njpatel> jcastro, heh, I'm not sure how much is actually there now. I've been rejecting things if they are very old
[16:46] <jcastro> oh ok
[16:46] <njpatel> (with a comment explaining why)
[16:46] <jcastro> looks way better than before
[16:46] <njpatel> indeed
[17:09] <cdbs> njpatel: pong
[17:09] <cdbs> njpatel: Is it about the GTK3 port? Yes, I'll be fixing that thing over the weekend
[17:10] <cdbs> jcastro: Hi there! Welcome back! How was Florida?
[17:10] <njpatel> nope, asking about this merge proposal lp:~bilalakhtar/unity/make-compilation-strict
[17:11] <njpatel> cdbs, ^
[17:11] <jcastro> good
[17:11] <cdbs> njpatel: what about it?
[17:11] <cdbs> njpatel: didrocks wanted it in, there's a really good reason for that merge
[17:11] <jcastro> njpatel: hey did gord's doxygen thing merge in? there's an open work item for it
[17:11] <njpatel> cdbs, I'm not sure what you last comment means, do we still need it in trunk or not?
[17:11] <cdbs> njpatel: we need it
[17:11] <cdbs> njpatel: in its current state, yes
[17:11] <njpatel> jcastro, it's approved since yesterday, not sure if he's merged it or not (it's fricking awesome)
[17:12] <njpatel> cdbs, but only for 4.6 and above, right?
[17:12] <njpatel> it fails with lower than that?
[17:12] <cdbs> njpatel: no, it works with 4.4+
[17:12] <cdbs> njpatel: my comment was concerning the backwards-compatibility which was fixed in the second commit
[17:12] <njpatel> cdbs, oh, so it's fine to go in?
[17:12] <cdbs> njpatel: yup
[17:13] <cdbs> O' hey, I forgot
[17:13] <cdbs> Today's a Review Friday!
[17:13] <cdbs> That's why njpatel is busy winding across the MPs :D
[17:20] <njpatel> cdbs, Review Friday?!
[17:20] <njpatel> jcastro has basically made every day Review day! :)
[17:20] <cdbs> njpatel: Didn't we plan these at the UDS sesson?
[17:20] <jcastro> YEAH!
[17:20] <jcastro> the day is monday though, just needed to clear the backlog
[17:20] <njpatel> cdbs, Review Monday was what we did in the session
[17:21] <njpatel> cdbs, but we did Review Tuesday this week as Monday was holiday in US and UK
[17:21] <njpatel> cdbs, okay, so I'll make sure your branch lands. that's one more ticked off the list! :)
[17:22] <cdbs> njpatel: No big hurry, any case, how many SRUs more before work starts to get Unity running well on Oneiric?
[17:22] <njpatel> cdbs, things are still flying in so I think we should do another SRU round next week, and then slow down a bit and concentrate on O
[17:22] <njpatel> Will speak to didrocks about it
[17:22] <njpatel> who seems to be striking again
[17:23] <jcastro> [bilalakhtar] Decide on the milestones of the Papercuts project for the Oneiric cycle: TODO
[17:23] <jcastro> [njpatel] milestone bitesize bugs: TODO
[17:23] <jcastro> FYI guys
[17:23] <cdbs> hmm yeah
[17:23] <njpatel> isn't that an on-going thing jcastro ?
[17:23] <cdbs> weekend task
[17:24] <jcastro> njpatel: I dunno, I don't recall if you wanted to just check them all at the beginning of the cycle or what
[17:24] <dcordes> #
[17:24] <jcastro> it's filed for A1, so maybe that's what you meant?
[17:24] <njpatel> that sounds like something I'd do
[17:25] <njpatel> yeah, okay, will try and get it done
[17:25] <njpatel> I can't believe A1 has happened already
[17:25] <njpatel> there's too much to do
[17:25] <jcastro> njpatel: want me to move it to A2?
[17:26] <njpatel> please
[17:26] <njpatel> have a good weekend all
[19:01] <jcastro> Nafai: your post on the quicklists should be on ayatana-dev, not ayatana.
[19:01] <jcastro> ayatana is like design discussion, ayatana-dev is where the DX team answers tech questions.
[19:03] <Nafai> doh
[19:03] <Nafai> :(
[19:04] <Nafai> thanks.  should I re-send it to -dev?
[19:04] <jcastro> yeah if you want DX to look at it
[19:04] <Nafai> ok, thanks for the pointer.
[19:04] <Nafai> sorry for the mis-post
[19:04] <jcastro> my rule of thumb: "discussion on ayatana, real work on ayatana-dev." :)
[19:04] <jcastro> no worries
[19:05] <jcastro> it's dumb that we don't  have "unity" and "unity-dev" imo
[19:09] <Pretto> jcastro: take a look at your pvt please ;)
[19:10] <Andy80> jcastro: yeah! we should have them.... a new developer that aims to contribute to Unity would come to #unity first... he would not imagine #ayatana :)
[19:12] <Nafai> jcastro: thanks again, I think I'm going to take a look at the Opportunities wiki page this weekend and see where I can help
[19:33] <PalinBachman2012> is Windows with Fixed Viewport in Place Windows messed up
[19:44] <rickspencer3> kenvandine, hi
[19:44] <kenvandine> hey rickspencer3
[19:45] <rickspencer3> kenvandine, anyone ...
[19:45] <rickspencer3> I just started to try to build unity/nux locally
[19:45] <rickspencer3> following directions here:
[19:45] <rickspencer3> http://askubuntu.com/questions/28470/how-do-i-build-unity-from-source/28472#28472
[19:45] <rickspencer3> when I tried autogen on nux, I got a package error:
[19:46] <rickspencer3> configure: error: Package requirements (glib-2.0 >= 2.25.14
[19:46] <rickspencer3>                   gdk-pixbuf-2.0
[19:46] <rickspencer3>                   gl
[19:46] <rickspencer3>                   glew
[19:46] <rickspencer3>                   glewmx
[19:46] <rickspencer3>                   xxf86vm
[19:46] <rickspencer3>                   sigc++-2.0
[19:46] <rickspencer3>                   ) were not met:
[19:46] <rickspencer3> No package 'xxf86vm' found
[19:46] <rickspencer3> jcastro, hey ^
[19:46] <rickspencer3> are these instructions out of date?
[19:46] <kenvandine> sudo apt-get build-dep nux
[19:46] <rickspencer3> *sigh*
[19:46] <kenvandine> might find what you need
[19:46] <rickspencer3> I thought I did that
[19:46]  * rickspencer3 tries
[19:46] <jcastro> they were up to date as of a week or so ago, did something change?
[19:46] <rickspencer3> holy crap, I did not
[19:46] <rickspencer3> 491 megs of dependencies!
[19:47] <kenvandine> :)
[19:47]  * jcastro adds some build dep action
[19:47] <rickspencer3> wtf, why do I need to install all this latex goo for nux?
[19:47] <jcastro> I know, I had to do that yesterday
[19:47] <kenvandine> one of the build deps must depend on it
[19:47] <jcastro> it pulled in this like 191mb latex doc package too
[19:47] <kenvandine> actually that would be doxygen
[19:47] <rickspencer3> so, er
[19:47] <rickspencer3> why?
[19:47] <kenvandine> which generates the docs
[19:47] <rickspencer3> 491megs of deps to build documenation?
[19:48] <rickspencer3> whatever
[19:48]  * kenvandine shrugs
[19:49] <rickspencer3> oh well
[19:49]  * rickspencer3 drums fingers
[19:49] <jcastro> should I just replace the build deps in the instructions with just sudo apt-get build-dep nux unity compiz, etc?
[19:50] <rickspencer3> jcastro, that seems a bit easier
[19:50] <jcastro> because that wants to bring in like, a bunch of KDE stuff
[19:50] <rickspencer3> with a wornign that if you don't have doxygen installed, it'll need 500 megs to download :/
[19:51] <rickspencer3> hmmm
[19:51] <rickspencer3> jcastro, I dunno, whatever you think will get people hacking hte fastest
[19:51] <rickspencer3> I'll take a break while I am downloaded all this extra goo
[19:51] <jcastro> disk is cheap!
[19:52]  * bcurtiswx would grab a cherry coke if he was rickspencer3
[19:52] <maco> jcastro: now that i have acquired a 500GB disk for my laptop, i agree!
[19:53] <maco> now i can let my pbuilder cache go crazy
[19:53] <bcurtiswx> pbuilder would be nice if i didn't have to DL all deps :P
[19:53] <bcurtiswx> every time
[19:53] <jcastro> squid-deb-proxy bro!
[19:54] <kenvandine> bcurtiswx, what jcastro said :)
[19:54] <Nafai> Hey rickspencer3, kenvandine!
[19:54] <kenvandine> itrocks
[19:54] <kenvandine> it rocks
[19:54] <kenvandine> hey Nafai
[19:54] <rickspencer3> hi Nafai!
[19:54] <Nafai> kenvandine: over the ubupneunomia?
[19:54] <Nafai> jpw
[19:54] <Nafai> er
[19:54] <Nafai> how's it going guys?
[19:54] <kenvandine> Nafai, mostly
[19:54] <Nafai> good!
[19:55] <hicham> hi kenvandine
[19:55] <maco> bcurtiswx: in theory the default is to cache
[19:55] <bcurtiswx> jcastro, sicne i dont' know about squid-deb-proxy got a how-to/wiki for it?
[19:56] <jcastro> rickspencer3: you can always submit an edit to the answer if it's wrong and someone will check it and approve it. Regardless I've asked htorque to take a look at the dependencies again.
[19:56] <rickspencer3> hey jcastro
[19:56] <rickspencer3> no thanks, I don't have the confidence
[19:56] <jcastro> bcurtiswx: http://askubuntu.com/questions/3503/best-way-to-cache-apt-downloads-on-a-lan
[19:56] <maco> bcurtiswx: /var/cache/pbuilder/aptcache/
[19:56]  * rickspencer3 steps away
[19:56] <maco> bcurtiswx: in theory the stuff you download stays there
[19:56] <bcurtiswx> jcastro, thx
[19:57] <Nafai> it seems like when I built unity/nux last week there was something missing from that list, but I forget :(
[19:57] <maco> i havent tested the manpage's claim yet
[20:02] <hicham> DBO: when bamf will start being ported to the glib matching api ?
[20:02] <DBO> yesterday
[20:02] <DBO> (seriously)
[20:05] <hicham> DBO: ?
[20:05] <hicham> DBO: sorry, I didn't understand what you just said
[20:05] <DBO> i started working on a simple port yesterday
[20:05] <hicham> great news
[20:05] <hicham> DBO: can I find it somewhere ?
[20:06] <hicham> DBO: so that I can see if mozilla apps will be correctly matched
[20:10] <jcastro> rickspencer3: I've sent a mail to the DX team asking them to give the document a run through.
[20:10] <jcastro> Also CCed didrocks, maybe there's a way to tighten up the build deps to be not so massive
[20:13] <DBO> hicham, not yet, it doesn't work yet
[20:14] <hicham> DBO: thanks
[20:53] <evaluate> Hello.
[20:53] <rickspencer3> re
[20:53] <evaluate> Any idea why I get these strange errors when trying to build libappindicator on Debian: http://rspwn.com/debian/libappindicator_0.3.0-1_amd64.build ?
[20:55] <evaluate> This is the first time I try this, so if I am doing something awfully wrong I am sorry, I was just curios as to why libappindicator isn't included in Debian yet and thought about helping out...
[20:56] <rickspencer3> hi evaluate
[20:57] <rickspencer3> nice nick btw
[20:57] <evaluate> Thanks! :-)
[20:57] <rickspencer3> I can't answer your question, but wanted to give you a heads up that it's late(ish) on Friday evening
[20:57] <rickspencer3> so, don't feel blown off if you don
[20:57] <rickspencer3> 't get an anwer right away
[20:57] <evaluate> It's late on Friday evening here too...
[20:58] <rickspencer3> :)
[20:58] <rickspencer3> jcastro, anyone around who would be able to look at this for evaluate
[20:58] <rickspencer3> ?
[21:04] <jcastro> yep one sec
[21:04] <jcastro> tedg: kenvandine?
[21:04] <tedg> jcastro, He rocks.
[21:05] <jcastro> tedg: can you give evaluate a hand?
[21:05] <jcastro> though this sounds more of a kenish problem
[21:05] <tedg> Yeah, probably, but I can look.
[21:06] <tedg> These are build-deps problems:
[21:06] <tedg> No package 'indicator3' found
[21:06] <tedg> No package 'dbusmenu-gtk3-0.4' found
[21:07] <tedg> The updated versions of those packages should have those pkgconfig files.
[21:07] <evaluate> Just out of curiosity, does the libindicator require some GTK patches or anyting like that, or *should* it normally work?
[21:08] <tedg> Otherwise it looks like vapigen and gobject-introspection are fighting.  And that is a kenvandine question.
[21:08] <tedg> evaluate, libindicator should be fine, appmenu-gtk does need some GTK patches.
[21:08] <evaluate> I see.
[21:09] <jcastro> evaluate: if he's not around in a bit here's the right mailing list: https://launchpad.net/~ayatana-dev
[21:09] <evaluate> Hmm, I can find libindicator3 in Debian, but dbusmenu-gtk3-0.4 doesn't seem to be available. I wonder why.
[21:09] <kenvandine> evaluate, do you have libindicator3-dev installed?
[21:10] <kenvandine> and libdbusmenu-gtk3-dev
[21:10] <tedg> evaluate, They might not be updated to the latest versions that dual build for GTK2/3?
[21:10] <kenvandine> ah
[21:11] <evaluate> kenvandine, those two packages don't seem to be available either (at least not in the normal repositories)
[21:11]  * evaluate does some googling
[21:18] <evaluate> Thanks for the help for now, I'll try getting those 2 packages installed and come back if I still have questions. :-)
[21:18] <evaluate> s/2/3/
[21:29] <evaluate> kenvandine, hmm, these packages seem to have other names in Debian, but I had them installed already.
[21:30] <kenvandine> what names?
[21:31] <evaluate> For example libdbusmenu-gtk3-dev seems to be libdbusmenu-gtk3 in Debian.
[21:32] <kenvandine> no, that would be the library
[21:32] <kenvandine> but not the dev package
[21:33] <Viper550> so I noticed you're using GTK3 stuff now?
[21:34] <evaluate> kenvandine, I'd guess the dev package would be libdbusmenu-gtk-dev
[21:34] <kenvandine> should be  libdbusmenu-gtk3-dev
[21:34] <Viper550> but what I want to know is, who is in charge with porting the theme?
[21:36] <evaluate> kenvandine, are these ubuntu packages packaged directly from upstream or synched/merged from Debian?
[21:36] <rickspencer3> kenvandine, should I be hacking on unity trunk or on "https://code.edge.launchpad.net/~unity-team/unity/branch-3.0" ?
[21:37] <kenvandine> evaluate, ubuntu is upstream, but the debian pkg-ayatana team has been working on them in debian
[21:37] <kenvandine> looks like the gtk3 builds in debian are commented out of their package
[21:37] <kenvandine> libdbusmenu-gtk3 is the gtk2 build, libdbusmenu-gtk3-3 is the gtk3 build
[21:38] <kenvandine> and libdbusmenu-gtk-3-dev is the gtk3 dev package
[21:38] <kenvandine> but those aren't built in debian
[21:38] <kenvandine> not sure why
[21:38] <kenvandine> rickspencer3, humm
[21:38] <rickspencer3> I ask because trunk doesn;t build and was just updated 4 hours ago :(
[21:38] <evaluate> kenvandine, I see. I guess I'll best talk to the debian-ayatana guys then. Thanks again for your help!
[21:39] <kenvandine> sorry... let us know if we can help more
[21:39] <kenvandine> rickspencer3, i suspect the 3.0 branch is what is in natty
[21:39] <rickspencer3> ok
[21:40] <rickspencer3> I'm starting with that, it seems to be building
[21:40] <kenvandine> ok
[21:40] <kenvandine> trunk should still be buildable though...
[21:40] <rickspencer3> "should be"
[21:40] <rickspencer3> Friday afternoon, though :)
[21:40] <kenvandine> yeah :)
[21:41] <rickspencer3> oh fudge
[21:41] <rickspencer3> I never did make install with the new nux
[21:41] <rickspencer3> maybe that was the problem
[21:42] <kenvandine> ah
[21:47] <rickspencer3> I have a sketchy feeling about this :)
[21:47]  * rickspencer3 tries out newly built unity
[21:49] <kenvandine> work?
[21:50] <htorque> rickspencer3: hi, could you build nux? this failed for me yesterday.
[21:50] <rickspencer3> kenvandine, well, I can't tell yet ;)
[21:50] <rickspencer3> htorque, nux did build for me
[21:51] <rickspencer3> I built nux from trunk, and I built unity/compiz from the 3.0 branch
[21:51] <htorque> rickspencer3: maybe another gcc 4.6 problem (i'm on oneiric)
[21:51] <rickspencer3> htorque, I see, I'm still on Natty
[21:51] <rickspencer3> "still"
[22:12] <evaluate> kenvandine, this is with the gtk3 libs enables in control and rules: http://rspwn.com/debian/libdbusmenu_0.4.3-1_amd64.build
[22:12] <rickspencer3> yeah!
[22:13] <rickspencer3> I can now break the launcher and run my private broken launcher!
[22:13] <evaluate> Am I right in the assumption that I'm missing the gtk-3.0 headers?
[22:13] <evaluate> rickspencer3, lol
[22:27] <rickspencer3> jcastro, kenvandine hey, do either of you know if there is some kind of overview of the unity codebase to help a sucker like me get oriented?
[22:29] <htorque> how would i build unity w/o documentation? configuration fails without doxygen installed (which shouldn't happen according to https://code.launchpad.net/~gordallott/unity/unity.optional-doxygen/+merge/62712)
[22:48] <marekw2143> hello
[22:49] <marekw2143> I'd like to write application that would do things similar to those which happen after pressing super + w
[22:49] <marekw2143> where can I find some api of unity and (the best) source code of function that is launched after pressing super + w ?
[23:25] <jcastro> rickspencer3: there is no overview, njpatel has a work item this cycle to make one (with a diagram, etc.)
[23:25] <rickspencer3> jcastro, thanks
[23:25] <rickspencer3> tbh, even a comment here and there would be nice
[23:25]  * jcastro nods
[23:25] <jcastro> I would even settle for a diagram
[23:26] <hicham> hi jcastro
[23:26] <hicham> jcastro: what part do you take care of in unity ?
[23:27] <jcastro> hicham: I connect people mostly
[23:27] <jcastro> hicham: and odd jobs. :)
[23:28] <hicham> jcastro: what is the nick of nux developer ?
[23:29] <jcastro> you're looking for jaytaoko
[23:29] <jcastro> but I think he's on weekend duty already
[23:32] <jcastro> Home of Unity and Ayatana || http://unity.ubuntu.com and http://wiki.ubuntu.com/Ayatana || Bitesize Bugs you can help with: http://goo.gl/i1WA1 and http://goo.gl/tiheb || Not getting an answer? Post on the https://launchpad.net/~ayatana-dev mailing list
[23:32] <jcastro> whoops
[23:37] <czajkowski> jcastro: what do you need doing
[23:37] <hicham> thanks jcastro
[23:38] <jcastro> czajkowski: I need "Not getting an answer? Post on the https://launchpad.net/~ayatana-dev mailing list" this tacked onto the topic
[23:38] <czajkowski> ta da
[23:39] <czajkowski> :)
[23:39] <jcastro> did you /topic? that didn't work for me
[23:39] <czajkowski> yup
[23:39] <jcastro> hmm, maybe I'm not in the cool club or something
[23:39] <jcastro> thanks!
[23:39] <czajkowski> now back to my day of being off line
[23:39] <czajkowski> jcastro: no bother :)