Monday, 2009-06-15

../irclogs/#mantishelp.2009-06-15.log
--- scribe started ---06:29
--- scribe started ---08:00
nuclear_eclipsemorning all12:31
nuclear_eclipsepaul_: there?12:31
[KK]Kirilllo12:31
paul_nuclear_eclipse: JOHN!!!!!!!!!!!!!!!!!!!!12:38
paul_nuclear_eclipse: I need to push my branch ;/12:38
[KK]Kirill>:D12:38
paul_it's getting long12:38
[KK]Kirillhi Paul12:38
paul_lo12:38
nuclear_eclipsepaul_: it's generally best to keep multiple branches for each topic, specifically for this reason.....12:38
paul_I do12:39
paul_:)12:39
paul_dates+bugobjects were seperate branches12:39
paul_I merged bugobjects into my 'trunk' as I was going to push on saturday12:39
nuclear_eclipseso did you ever mail the dev list about bugobjects like Victor asked/wanted you to?12:41
paul_nope12:42
paul_my server broke on sunday12:42
paul_until this morning12:42
nuclear_eclipsewyh didn't you mail the dev list on thursday/friday when he first asked you?12:42
paul_he asked on saturday didn't he12:42
nuclear_eclipseno, he asked during the week, because I was at work when he did12:43
paul_I guess people could check out the branch12:46
paul_it's got graphs work in it too12:46
nuclear_eclipse*that's* why you should be keeping separate branches, paul12:46
paul_I was12:46
paul_until the point people said commit bugojects ;p12:46
nuclear_eclipseyou shouldn't just be heaping all your work onto one branch and expect someone to be able to review a single part of it...12:47
paul_well 2 months ago is when bugobjects branch first came to light12:48
nuclear_eclipseI'm not arguing that12:49
nuclear_eclipseI'm simply wanting to get 1.2rc out, and apparently Victor wants you to mail the dev list about bugobjects before you do anything more with it, so please do that ASAP, or I'll just release the Rc without it...12:50
paul_more importantly12:53
paul_I think we hsould do a 1.1 release12:54
nuclear_eclipsewhat do you mean?12:54
paul_I found a bug in a 2005 security fix at the weekend :)12:54
nuclear_eclipsewhy does that matter?12:55
nuclear_eclipsejust fix it in master, and leave 1.1 alone12:55
paul_it could be a security issue though no?12:55
nuclear_eclipseI don't know, it depends on what the bug is; but tbh, that the bug has been there since 2005 tells me that it's *really* not that important that we should make yet another 1.1 release....12:56
paul_I agree12:56
paul_that and the fact I've rewritten the broken code12:58
paul_so it's not immediately obvious12:59
mantisbotNew bug: Bug 10590 - vpennel - open - new13:06
mantisbotNew bug: Probleme on date custom field update - http://www.mantisbt.org/bugs/view.php?id=1059013:06
paul_nuclear_eclipse: i've *almost* finished phpdoc+db_query removal too13:06
* paul_ was bored over weekend13:06
mantisbotNew bug: Bug 10591 - vpennel - open - new13:11
mantisbotNew bug: File custom field - http://www.mantisbt.org/bugs/view.php?id=1059113:11
CIA-61Mantisbt: jreese * re345f2f865d7 / (54 files in 5 dirs): Fix #10303: Use UTF-8 compatible string functions.13:57
CIA-61Mantisbt: jreese * r4fe8e0277fc7 /library/utf8/ (86 files in 12 dirs): Issue #10303: Added phputf8 0.5 package.13:58
[KK]Kirillbug 1030314:29
mantisbotBug 10303 - jreese - fixed - resolved14:29
mantisbotCreate and use string_api wrappers for multibyte string functions - http://www.mantisbt.org/bugs/view.php?id=1030314:29
mantisbotNew bug: Bug 10592 - cbasset - open - new15:01
mantisbotNew bug: mc_enum functions doesn't take customization into account - http://www.mantisbt.org/bugs/view.php?id=1059215:01
paul_nuclear_eclipse: *sighs*15:11
paul_can you pull that commit?15:11
nuclear_eclipsewhat commit?15:11
paul_15:07 < CIA-61> Mantisbt: jreese * re345f2f865d7 / (54 files in 5 dirs): Fix #10303: Use UTF-8 compatible string functions.15:12
paul_15:07 < CIA-61> Mantisbt: jreese * r4fe8e0277fc7 /library/utf8/ (86 files in 12 dirs): Issue #10303: Added phputf8 0.5 package.15:12
nuclear_eclipsewhat do you mean by pull it?15:12
paul_not include it in for now15:12
nuclear_eclipsewhy?15:12
paul_for the reasons i've said last few days15:12
paul_besides that commit will probably break my local branch completely15:12
nuclear_eclipsepaul_: if you would have listened to me the past few days, I've told you that we can bo back and fix any of the concerns you have with that implementation15:13
nuclear_eclipseand it really shouldn't be that difficult to fix any merge conflicts -- I really don't think it's worth reverting over that15:13
paul_the point is that's not going to merge in anyway cleanly with what i've done over weekend15:13
nuclear_eclipseso fix any conflicts15:14
paul_lol15:14
nuclear_eclipseand you still haven't mailed the dev list like victor asked you to....15:16
* paul_ isn't mailing from his work mail address15:16
nuclear_eclipseso use your mantisforge address...15:16
nuclear_eclipsedidn't you set up webmail and all that?15:16
paul_yep although the real reason is i need to sync my mantisforge branch15:16
paul_but seriously15:18
paul_my first aim is to drop that library15:18
nuclear_eclipsepaul_: please, ignore the utf8 stuff right now15:19
paul_guess I can work on replacing those library functions with the versions i've worked out over the last month or so tonight ;/15:19
nuclear_eclipseand for the love of god, don't drop the library -- we *really* can't just reinvent the wheel every damn time we come across some new topic...15:20
nuclear_eclipseand seriously, I did some testing on my server, and there was literally *no* performance difference between with or without the new utf8 stuff, so like I said, the performance of an individual function is *really* not important15:21
paul_the point still remains that the library isn't being updated and we've already done work on supporting php5,5.3 and 6 with unicode for functions15:28
nuclear_eclipsethe point still remains that by rolling our own library, we will still not have anything manitained!15:29
nuclear_eclipseand seriously, we can modify the existing library as it is if we really need to15:30
nuclear_eclipseand PHP6 still isn't even in any sort of stable state yet!15:30
* paul_ gets home17:22
paul_and going out for dinner tonight ;/17:22
paul_18:32  * paul_ gets home17:23
paul_18:32 < paul_> and going out for dinner tonight ;/17:23
paul_will you be about in a few hours john?17:23
nuclear_eclipseyep17:35
paul_cool17:35
paul_you can work out how to merge my branch then ;p17:36
nuclear_eclipsedhx_m: around?18:00
siebrandcool. Someone just finished the Czech localisation.18:26
nuclear_eclipse:)18:26
paul_nuclear_eclipse: around19:58
nuclear_eclipseyo20:04
* siebrand burps softly.20:07
nuclear_eclipsehi siebrand20:07
siebrandhola20:07
paul_nuclear_eclipse: so, how do i merge this branch20:27
nuclear_eclipse`git pull --rebase` -- if there are conflicts, fix the files that have conflicted, `git add <file>` and `git rebase --continue`20:29
paul_is there a way to avoid that step20:30
nuclear_eclipsewhich step?20:30
paul_ix the files that have conflicted, `git add <file>`20:30
nuclear_eclipsewell, if there are conflicts, no, you can't skip that step....20:30
paul_can we pick out the two utf8 commits20:30
paul_then apply them afterwards20:30
nuclear_eclipsethat will create just as many, if not more conflicts....20:31
paul_erm nope20:31
nuclear_eclipseerm, yep20:31
nuclear_eclipsetrust me20:31
paul_trust me it won't :)20:31
nuclear_eclipsepaul_: if they conflict applying your changes on top of utf8, applying utf8 on top of your commit will (guaranteed) cause as many or more conflicts as20:32
paul_one's mainly a string replace though...20:32
nuclear_eclipseit's just the way that mergeing works...20:32
nuclear_eclipsepaul_: if you really don't want to deal with it, push it to a public branch, and I'll take some time to resolve any merge conflicts...20:43
paul_I dont mind doing it20:51
paul_what I just need is victor to agree to push changes20:51
paul_nuclear_eclipse: branch is at http://git.mantisforge.org/w/mantisbt/paul.git?a=shortlog;h=refs/heads/15June but I'll sort out utf820:53
* paul_ just needs rest of stuff agreed :P20:53
nuclear_eclipsepaul_: just email that link, and a link of the diff between master and your branch to the dev list, and I'll prod people to review it asap for the RC20:54
paul_you've not looked at it ;p20:54
nuclear_eclipseI have, it's just a shortlog, which makes it hard to tell what's from master and what's from your branch...20:59
paul_3 days agoJohn ReeseMerge commit 'dhx/rm-hardcoded-enum' into enumscommit (base | diff) | commitdiff | tree (base | diff) |21:00
paul_above that is the branch21:00
nuclear_eclipseok21:00
paul_http://git.mantisforge.org/w/mantisbt/paul.git?a=commitdiff;h=27213a2080fe6e1dd6e7bbcd3dbaeda6684690b1;hp=16677b02600202b5ebbb3fff9fe0d5c445bffa62 is the patch of the changes in branch to master21:00
nuclear_eclipseok, so mail both those links to the list21:04
paul_btw, did you look at the graphs changes?21:15
nuclear_eclipsenot yet21:15
paul_you've concluded however that I got bored over the weekend?21:16
nuclear_eclipseit is noticeable...21:16
paul_i've almost finished phpdoc warnings for /core!21:17
nuclear_eclipsetime to head home21:19
nuclear_eclipsepaul_: send that mail to dev list...21:19
paul_ok!ok!21:19
paul_just finishing phpdoc first21:20
paul_also we need to discuss php codesniffer rules21:20
nuclear_eclipsewell, that should be yet another post to the dev list...21:20
* nuclear_eclipse leaves 21:20
phl4kxhi all23:16
phl4kxwhat option I have to activate for send email to a INFORMATED when I change a status bug to a RESOLVED?23:17
nuclear_eclipselook at $g_notify_flags and $g_default_notify_flags -- both of which are also canfigurable through the configuration management UI23:21
phl4kxyes I see thanks23:25

Generated by irclog2html.py