Monday, 2010-09-20

*** Quits: daryn (~daryn@h34.10.96.216.dynamic.ip.windstream.net) (Ping timeout: 276 seconds)00:07
*** Joins: daryn (~daryn@h34.10.96.216.dynamic.ip.windstream.net)00:08
*** Quits: daryn (~daryn@h34.10.96.216.dynamic.ip.windstream.net) (Quit: Ex-Chat)00:35
*** Quits: tavasti (~tavasti@217.152.202.221) (Ping timeout: 240 seconds)00:41
*** Joins: kirillka (~Miranda@195.242.142.17)01:13
*** Joins: giallu (~giallu@fedora/giallu)02:30
*** Quits: siebrand (~beis@sm.xs4all.nl) ()02:38
*** Joins: Cupertino (~Cupez@unaffiliated/cupertino)02:58
*** Joins: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk)03:06
*** Joins: mantisbt_62048 (cb2c3402@gateway/web/freenode/ip.203.44.52.2)03:06
*** Quits: mantisbt_62048 (cb2c3402@gateway/web/freenode/ip.203.44.52.2) (Client Quit)03:09
dhx1giallu: I noticed you backported some security patches to 1.1.x... there are actually 20+ XSS issues from towards the end of last year that haven't been backported (too time consuming)03:16
gialluwell. I can't upgrade released branches to 1.203:17
gialluand I react to bugs reports, those were reported in BZ03:17
dhx1giallu: how long before they become unsupported?03:17
gialluFedora. 13 months03:17
dhx1from now? ugh03:18
gialluno, from release03:18
gialluso it means F12 goes EOL in 3 months (more or less)03:18
dhx1F13 = MantisBT 1.2.x I assume?03:18
gialludhx1, nope03:18
gialluwhen we released 1.2?03:19
giallu1.2.0 I mean03:19
gialluIIRC it was near F13 timeframe03:19
dhx1Feb 22nd03:19
gialluand I decided it was too risky to put there03:19
gialluright now, I did not change my mind on that ;)03:20
gialluso I'd need to push 1.2 to F14 (I'm a but late)03:20
dhx1Hmmm so Fedora 13 is stuck with 1.1.8 until March next year?03:20
giallubasically03:20
gialluyes03:20
giallubut I guess DEbian folks are in the same (or worst) boat03:20
dhx1yep, it's a big problem for both distros IMO03:21
dhx11.1.8 => 1.2.0 is a giant leap in terms of security fixes03:21
dhx11.3.0 will be another leap when X-Content-Security-Policy work is done03:22
dhx1but at least 1.2.x is maintainable at the moment03:22
dhx1(as it has been <1yr since 1.3.0 branched)03:22
dhx11.2.0 branched many years ago03:22
micahggiallu: I would like to help the Debian maintainer get 1.2.x in, but haven't had time to look at the dbconfig related stuff which is the hold up03:36
giallumicahg, yeah. I know that's another major issue debian side (fortunately, I haven't that in Fedora )03:37
micahggiallu: what's holding you back, time?03:38
giallumicahg, lately, yes. But also, I recognized the huge leap between 1.1 and 1.2 probably meant more security issues03:39
gialluand I actually avoided some of them03:39
micahggiallu: oh, I would've thought the opposite since it's actively maintained03:40
giallumicahg, well. yeah. the fixes were pretty fast, thanks to David and John mostly03:41
dhx1yep I could probably find 30 or so XSS issues in 1.1.8... I actually gave up backporting when I realised how many there were03:42
dhx1but that's not the only reason why 1.1.8 is a dud... I've added a number of extra security features in 1.2.x such as the HttpOnly cookie flag03:43
dhx1which don't really fit into the backport-to-stable methodology03:43
gialludhx1, I realize that. however, that's just more security. I'm just happy with "secure enough" unless I'm paid for the "more" part03:44
giallu:)03:44
dhx1agreed, fixing the XSS issues is the primary concern03:44
giallubesides03:45
gialluI really need to work on unbundling libraries03:45
gialluwhich just hit me with nusoap :(03:45
dhx1yeah libraries are a real pain03:45
* micahg hopes for Natty I can get Mantis 1.2.x in03:51
giallumicahg, see for instance https://bugzilla.redhat.com/show_bug.cgi?id=620993 :)03:51
micahggiallu: yes, but isn't there an assumption that there are similar exploits for 1.1.x that no one is reporting?03:52
dhx1example bugs: http://git.mantisbt.org/?p=mantisbt.git&a=search&h=refs%2Fheads%2Fmaster-1.2.x&st=commit&s=XSS03:53
dhx1they won't backport nicely because much of 1.1.x was redesigned for 1.2.x03:54
dhx1for instance, the view bug page is completely different in each version (as are the report, update, etc pages)03:54
dhx1I prefer Gentoo's approach which allows them to add new upstream versions at will03:55
dhx1but they may not mark them as stable03:55
dhx1if there is a major security concern with the current stable version they can either mask it (to warn users and block installation of the package by default) or accelerate the timeframe to which an upgrade to the newer major version is done03:56
dhx1I'm not sure if they do the former03:57
micahgdhx1: well, Ubuntu has the flexibility if support is impossible to upgrade04:00
micahgbut it's best to backport if possible04:01
dhx1the problem with long term support distributions (ie. an entire release is supported for X months) is that the maximum time between major upgrades of a package is 2X in worst case04:02
dhx1(in the event that a major release is put out just after the distribution freeze)04:02
dhx1and there usually isn't enough manpower to handle that extra workload of backporting unless you're RedHat and are paying people to do the backporting for you04:03
dhx1(kernel, etc)04:03
*** Joins: rolfkleef (~rolf@urtica.xs4all.nl)04:03
micahgdhx1: like we just missed 1.2 for Lucied04:05
micahgLucid04:05
dhx1micahg: at least that is only 1 year worst case04:06
dhx1or are you referring to Ubuntu LTS?04:06
micahgdhx1: Lucid was the LTS, support till Apr 201304:06
dhx1oh dear, poor Ubuntu LTS MantisBT users :p04:06
micahgdhx1: yes, well, when we get it in Natty, we can backport to Lucid04:07
dhx1I see :)04:07
micahgbut I have to get it so the Debian maintainer can continue doing most of the work since I'm very overloaded ATM04:08
micahgwhich means doing things the Debian way04:08
micahgwhich nuclear_eclipse does not like per se04:08
dhx1I think the previous Debian maintainer gave up earlier this year?04:09
dhx1maybe I'm thinking of a different distribution though04:09
micahgdhx1: nope, but there was a new maintainer04:10
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection timed out)04:13
*** Joins: netadmin_ (~netadmin@41.225.4.62)04:14
kirillkanuclear_eclipse: check your mail. I send 2 patchs for product-matrix and source04:30
kirillkadhx1: hi04:30
dhx1kirillka: hi04:30
kirillkadhx1: I see issue. this my event04:31
*** Quits: kirillka (~Miranda@195.242.142.17) (Read error: Connection reset by peer)04:32
*** Joins: kirillka (~Miranda@195.242.142.17)04:33
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)04:43
*** Joins: netadmin_ (~netadmin@41.225.4.62)04:43
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)05:11
*** Joins: netadmin_ (~netadmin@41.225.4.62)05:14
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)05:43
*** Joins: netadmin_ (~netadmin@41.225.4.62)05:43
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)06:12
*** Joins: netadmin_ (~netadmin@41.225.4.62)06:12
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)06:41
*** Joins: netadmin_ (~netadmin@41.225.4.62)06:41
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 255 seconds)07:09
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)07:10
*** Joins: netadmin_ (~netadmin@41.225.4.62)07:10
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)07:39
*** Joins: netadmin_ (~netadmin@41.225.4.62)07:39
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)08:08
*** Joins: netadmin_ (~netadmin@41.225.4.62)08:08
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)08:37
*** Joins: netadmin_ (~netadmin@41.225.4.62)08:37
*** Joins: giallu (~giallu@fedora/giallu)08:58
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)09:06
*** Joins: netadmin_ (~netadmin@41.225.4.62)09:06
nuclear_eclipsegiallu: I'm here now09:21
killefizgiallu: any plans to update mantis in fedora? I can do the plain update if you want but IIRC you were working on a spec with split-libs?09:23
giallunuclear_eclipse, I just wanted to know if you are keen to make a release with the fixes I pushed on 1.1.x09:25
giallukillefiz, working on that09:25
giallukillefiz, will start splitting nusoap09:26
nuclear_eclipsegiallu: sure, is it time sensitive at all, or just when I get the chance?09:28
*** Parts: lftsy (~lftsy@ifrit.leurent.eu)09:29
*** Joins: daryn (~daryn@h158.249.190.173.static.ip.windstream.net)09:29
giallunuclear_eclipse, not  time sensitive. I'd like to fix the stuff I've got reports downstream on bugzilla.redhat.com, that is, I still miss the nusoap fix09:29
gialluthe rest I believe is fixed09:30
nuclear_eclipsegiallu: just let me know when you're ready for me to cut the release, and I'll add it to my to-do list09:30
killefizgiallu: we do need to act on 633003 633011 and 63434009:30
giallukillefiz, I fixed upstream (i.e. here) 003 and 34009:31
giallukillefiz, see http://git.mantisbt.org/?p=mantisbt.git;a=log;h=refs/heads/master-1.1.x09:32
nuclear_eclipsedhx1: here?09:32
nuclear_eclipsedhx1: I have a bone to pick with your tag deletion patch...09:32
dhx1nuclear_eclipse: hi09:32
dhx1ref?09:33
nuclear_eclipseyour commit reasoning is incorrect09:33
nuclear_eclipsee5ba672d6f709:33
nuclear_eclipsethe user deleting a tag does *not* always have access to manage tags09:33
killefizhmm - 634340 says "... fixed in 1.2.3" - ahh - you're planning to do another 1.1.x release - now I get it09:34
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)09:35
nuclear_eclipsedhx1: oh wait09:35
nuclear_eclipsenvm, I must be remembering inccorectly :x09:35
*** Joins: netadmin_ (~netadmin@41.225.4.62)09:35
nuclear_eclipsewell, yes/no09:35
nuclear_eclipsedhx1: I was thinking that users could delete tags they created via tag_edit_own_threshold,09:36
nuclear_eclipsedhx1: foot in mouth, sorry for not checking up on it before saying something09:37
dhx1I'm confused now :)09:37
nuclear_eclipsemove along now, nothing to see here09:37
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 272 seconds)09:37
nuclear_eclipseI didn't mean you giallu09:37
dhx1:)09:40
dhx1TODO: replace MantisGraph with jquery.flot09:41
dhx1http://code.google.com/p/flot/09:41
dhx1like everything jQuery, it's so easy to use09:42
dhx1there is a downside though, no static image generation09:42
nuclear_eclipsedhx1: in that case, I would propose you just add flot as the default option while still allowing users to switch to ezc or jpgraph09:43
kirillkadhx1: what about nation charset?09:43
kirillkanuclear_eclipse: you right09:44
kirillkanuclear_eclipse: Did you see patches?09:44
dhx1kirillka: it renders captions/labels using the browser so full UTF8 support is included by default09:44
dhx1kirillka: it actually uses the new HTML5 canvas element09:44
nuclear_eclipsekirillka: I have them in my inbox, but a bit busy atm09:44
kirillkadhx1: what's about support fonts, etc with national charset?09:44
dhx1nuclear_eclipse: perhaps, but those are quite broken implementations at the moment09:45
nuclear_eclipsedhx1: even more reason to make it just another option to select from09:45
kirillkanuclear_eclipse: ok. please write comments to mail for patches?09:45
dhx1kirillka: http://people.iola.dk/olau/flot/examples/setting-options.html  <=== shows the use of the Pi symbol09:45
kirillkadhx1: my users use IE 7 now09:45
dhx1nuclear_eclipse: no, I meant ezC/JpGraph render badly at the moment :p09:45
dhx1kirillka: yep so it won't work there09:46
kirillkadhx1: I send patch in dev list for Issue 1235209:47
nuclear_eclipsedhx1: canvas would render bad in most of the browsers people use where I work, too ;009:47
dhx1kirillka: sounds good, I'll look out for it09:47
dhx1nuclear_eclipse: it looks nice/renders very quickly in Chromium 7 nightly :)09:48
nuclear_eclipseI'm sure it does09:48
nuclear_eclipsebut 99% of users aren't running unstable branch of Chrome ;)09:48
dhx1a graph type that would be useful in mantis: http://people.iola.dk/olau/flot/examples/stacking.html09:48
kirillkadhx1: i don't sure this patch very nice for main concept of mantis structure, but it's work09:49
dhx1also spark line charts @ http://omnipotent.net/jquery.sparkline/ could be nice09:49
*** Quits: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk) (Quit: Rixie)09:50
nuclear_eclipsekirillka: just looked at the patches, but I haven't made that change yet because it would break the ability to use those plugins on 1.2.x09:51
kirillkanuclear_eclipse: one sec09:51
kirillkanuclear_eclipse: yes. you right09:54
nuclear_eclipsekirillka: I'd planned to make those changes once 1.3 goes RC status09:55
kirillkanuclear_eclipse: I already used short name, and don't think that 1.2.x don't support this.09:55
*** Quits: kirillka (~Miranda@195.242.142.17) (Quit: kirillka)09:59
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)10:04
*** Joins: netadmin_ (~netadmin@41.225.4.62)10:04
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)10:33
*** Joins: netadmin_ (~netadmin@41.225.4.62)10:33
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)11:02
*** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...)11:02
*** Joins: netadmin_ (~netadmin@41.225.4.62)11:02
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)11:31
*** Joins: netadmin_ (~netadmin@41.225.4.62)11:31
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Read error: Connection reset by peer)12:00
*** Joins: netadmin_ (~netadmin@41.225.4.62)12:00
*** Quits: netadmin_ (~netadmin@41.225.4.62) (Ping timeout: 240 seconds)12:33
nuclear_eclipsepaulr_: kick your server12:43
*** Joins: netadmin_ (~netadmin@41.225.4.62)12:46
*** Joins: pira_ (4546a4f6@gateway/web/freenode/ip.69.70.164.246)12:47
pira_Hello everybody ! (excuse my english), Ok, I've been asked if it's possible in mantis > manage projects > edit a project > planning > add role, then 'Add user to project' .... to associate an 'Administrator' to the new role...? (Here I can't). I've looked arround, and I'm finally here asking you guys :) Thanks in advance !12:51
nuclear_eclipsepira_: it should be possible as far as I know, what version are you using?12:52
*** Quits: micahg (~micah@ubuntu/member/micahg) (Read error: Operation timed out)12:56
pira_Hi nuclear_eclipse , ok we're running an old version like 1.04 !?12:58
pira_I'm still looking for the version a minute please (It's a custom one...)12:58
nuclear_eclipsepira_: backup your site and data, and upgrade please :P12:58
pira_Hey ... ! I would love to :) !!12:59
nuclear_eclipse1.0.4 is out of date, even for the extremely out of date 1.0 branch :P12:59
pira_But...at this time the developper added some feature and .... with an upgrade .... you know !12:59
nuclear_eclipsepira_: good luck then :)13:00
pira_Of course when I 'upgrade' the bug are still there, but...not all the features !13:00
pira_haha !13:00
nuclear_eclipseunfortunately, I can't help you with 1.0.x13:01
pira_Yep, I have a mission and I first wanted to upgrade in order to get the plugin manager working, but with the old work done on our version....was not possible13:01
pira_In case of : is there a directive for this 'planning' roles !?13:02
*** Joins: siebrand (~beis@sm.xs4all.nl)13:23
pira_Ok I've my answer, or kind of ... http://www.mantisforge.org:8080/cruisecontrol/artifacts/mantisbt/20100802185453/phpxref/nav.html?_functions/index.html line 1035, WHERE u.access_level<" . db_param()  .... So the admin can not be assigned to it, anyway, thanks nuclear_eclipse13:27
*** Joins: moto-moi (~hylke@cara.xs4all.nl)13:51
pira_Have a nice day14:00
*** Quits: pira_ (4546a4f6@gateway/web/freenode/ip.69.70.164.246) ()14:00
*** Joins: micahg (~micah@ubuntu/member/micahg)14:28
*** Joins: giallu (~giallu@fedora/giallu)15:02
*** Joins: phinney (~phinney@c-174-51-67-106.hsd1.co.comcast.net)15:03
*** Joins: siebrand_alt (~beis@sm.xs4all.nl)15:08
*** Quits: siebrand (~beis@sm.xs4all.nl) (Ping timeout: 252 seconds)15:09
*** siebrand_alt is now known as siebrand15:14
phinneyCan anyone help me with the Source Control Integration 0.16.2 plugin using Mantis 1.2.3 please?15:15
nuclear_eclipsehi phinney 15:16
phinneyI *think* I have it configured right but when I check in files via TortoiseSVN nothing happens.15:16
phinneyhi nuclear_eclipse15:16
nuclear_eclipsephinney: you need to either set up your svn post-commit hook, or a cronjob, to tell Mantis to pull in new data from the repository.15:16
phinneyeven though i have the plugin instaled?15:17
nuclear_eclipseyeah, the plugin only tells mantis how to pull data, it won't know when to pull data without something to tell it to do that15:17
phinneyok, so i should use post-commit.tmpl as the model right?15:18
nuclear_eclipseso you need to setup either a cronjob to do that on a regular time period, or use the example post-commit hook in the SourceSVN directory to set up your SVN repo to do it automaticall15:18
phinneyURL="http://mymantisurl.com/plugin.php?page=Source/checkin" Do I need to modify "Source/checkin" at all?15:23
nuclear_eclipseshouldn't need to15:26
nuclear_eclipsethe hook should pass all the needed info as part of the URL15:26
phinneyso i used post-commit.tmpl as the model, changing the paths as needed, saved the file as post-commit in the same dir and nothing happened.15:28
phinney(bare with me, this is my first time working with both TortoiseSVN and Mantis other than as a user)15:29
nuclear_eclipsephinney:  if you're using Linux/BSD/Mac, you need to set the post-commit file as executable (chmod +x post-commit), and also need to make sure that you have curl installed and in the system path15:30
*** Joins: cobexer (~cobexer@188-22-33-178.adsl.highway.telekom.at)15:32
phinneyso when i do which curl to get the curl dir, it returns /usr/bin/curl so in post-commit I should put CURL=/usr/bin/ ?15:34
nuclear_eclipse/usr/bin/curl15:34
phinneyok15:35
nuclear_eclipsephinney: also, look in /tmp/ for the log files that get created by the post-commit script; if they aren't getting created, then SVN probably isn't executing it at all15:36
nuclear_eclipsephinney: post-commit hooks are always a pain to get set up, so don't feel bad :P15:36
phinneyIs the PROJECT url the mantis project or the SVN project?15:39
phinneyPROJECT name, not url15:40
phinneyin post-commit15:40
nuclear_eclipsethe name of the repo in mantis15:40
phinneyOr is that the name that is listed when you click on the hyperlink Repositories?15:41
nuclear_eclipseyes15:41
phinneyahhh, that might be one issue i'm having  ;)15:41
phinneyok, it doesn't seem to be loggin anything15:58
nuclear_eclipsephinney:  you are making sure to copy the post-commit file into your SVN repo's hooks directory? :P16:01
*** Joins: paulr (~IceChat09@2001:470:9310:aaaa:e1f2:55c8:e3a6:3f)16:02
nuclear_eclipsepaulr: kick your server16:02
nuclear_eclipsebefore I kick you16:02
paulryea16:02
paulrI saw16:02
*** Joins: \cobexer (~cobexer@88-117-53-107.adsl.highway.telekom.at)16:15
phinneySo now when I commit via TortoiseSVN I'm getting the following error....post-commit hook failed (exit code 255) with no output.16:16
phinneyI went back and put the post-commit script into the hooks dir in my svn install16:17
phinneyi'm using the post-commit.tmpl from mantisdir/plugins/SourceSVN has my example16:17
*** Quits: cobexer (~cobexer@188-22-33-178.adsl.highway.telekom.at) (Ping timeout: 276 seconds)16:19
*** \cobexer is now known as cobexer16:35
*** Quits: cobexer (~cobexer@88-117-53-107.adsl.highway.telekom.at) (Remote host closed the connection)17:04
paulrnuclear_eclipse: seen dhx today?17:06
paulror daryun17:06
darynhm...who's daryun?17:15
giallulol17:18
* daryn smiles17:18
paulrhi darren17:20
paulrhi gianluca17:20
darynpaulr: you're just going all out today17:20
paulrnah, i'm not going anywhere17:20
paulrin for night now17:20
paulrI was out a chinese wedding yesterday though17:20
paulrthanks for asking :)17:20
darynso what's up?17:21
paulrreading http://www.mantisforge.org/irclogs/%23mantishelp.2010-09-20.log.html atm17:22
paulrso17:22
paulrgiallu17:22
paulrexplain what redhat/debian do17:22
paulrto mantis17:22
gialluagain? :P17:23
paulryea17:25
paulrlets start with17:25
paulrwhat's natty?17:26
daryncode name for debian release17:26
* giallu thinks is a Ubuntu one.17:31
giallubut I don't really know anything about Ubuntu/Debian17:32
darynyou're probably right, it does sound very ubuntuish.  i just saw it on debian lists.17:37
gialluDebian releases are named after toy story characters IIRC17:38
nuclear_eclipseNatty == 11.0417:39
paulrhow often do they do releases again17:39
paulroctober and april?17:39
nuclear_eclipse6 months17:39
nuclear_eclipseLTS every other april17:39
paulrso wait 9.04 is LTS?17:40
paulrthen 11.04?17:40
paulrwhat about debian?17:40
nuclear_eclipse10.04 was last LTS17:41
nuclear_eclipsedebian = unpredictable17:41
paulrso 10.04 has 1.2.0?17:41
nuclear_eclipseno17:41
paulrwtf?17:41
nuclear_eclipseno ubuntu has 1.217:41
paulrOK17:41
paulrI dont want to know17:41
nuclear_eclipsethe database changes are incompatible with the way debian does their package upgrade/database maintenance stuff17:41
nuclear_eclipseso they've chosen to stick with 1.1.x until they can reach some sort of conclusion17:42
nuclear_eclipseanywho, dinner time17:43
paulrcool17:43
paulrso ignoring debian17:43
paulrhow does one get stuff into ubuntu17:43
paulr:)17:43
paulrgiallu: and dare I ask what fedora do17:44
paulrwhen do they realise17:44
paulrerm17:44
paulrrelease17:44
gialluevery 6 months, release N goes EOL when N+2 is released + 1 month17:46
gialluusually a bit later than ubuntu17:46
*** Quits: moto-moi (~hylke@cara.xs4all.nl) (Ping timeout: 276 seconds)17:57
*** Joins: chmurli (render@26.80-203-21.nextgentel.com)18:00
chmurlihi18:00
*** Quits: siebrand (~beis@sm.xs4all.nl) (Ping timeout: 276 seconds)18:03
*** Joins: siebrand (~beis@sm.xs4all.nl)18:07
*** Quits: daryn (~daryn@h158.249.190.173.static.ip.windstream.net) (Quit: Ex-Chat)18:17
paulrright18:36
paulrI think I need to work out a time to come on to catch dhx18:36
paulr:)18:36
*** Quits: paulr (~IceChat09@2001:470:9310:aaaa:e1f2:55c8:e3a6:3f) (Quit: Copywight 2010 Elmer Fudd. All wights wesewved.)19:04
*** Parts: phinney (~phinney@c-174-51-67-106.hsd1.co.comcast.net)19:08
*** Quits: foobot (~supybot@leetcode.net) (Remote host closed the connection)19:29
*** Joins: foobot` (~supybot@leetcode.net)19:29
*** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection)20:00
*** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de)20:00
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 255 seconds)20:40
*** Joins: daryn (~daryn@h48.147.28.71.dynamic.ip.windstream.net)22:05
*** Joins: micahg (~micah@ubuntu/member/micahg)22:07
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 276 seconds)22:27
*** Joins: micahg (~micah@ubuntu/member/micahg)22:31
*** Quits: wolog (~wolog@87.106.58.253) (Ping timeout: 252 seconds)22:43
*** Joins: wolog (~wolog@87.106.58.253)22:43
*** Quits: rolfkleef (~rolf@urtica.xs4all.nl) (Ping timeout: 264 seconds)22:55
*** Quits: daryn (~daryn@h48.147.28.71.dynamic.ip.windstream.net) (Ping timeout: 272 seconds)23:25
*** Joins: daryn (~daryn@h48.147.28.71.dynamic.ip.windstream.net)23:30
*** Quits: daryn (~daryn@h48.147.28.71.dynamic.ip.windstream.net) (Quit: Ex-Chat)23:55

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!