| 00:00.49 | *** join/#maemo-ssu KenYoung (~rtm@pool-108-20-253-215.bstnma.east.verizon.net) |
| 00:01.48 | *** join/#maemo-ssu KenYoung (~rtm@pool-108-20-253-215.bstnma.east.verizon.net) |
| 00:15.15 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 00:38.21 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 01:07.35 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 03:54.50 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 04:48.45 | *** join/#maemo-ssu M13 (~Miranda@83.149.37.184) |
| 06:09.09 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-83-158.residential.rdsnet.ro) |
| 06:43.01 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 06:56.37 | *** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net) |
| 08:10.50 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 08:48.50 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-83-158.residential.rdsnet.ro) |
| 08:53.08 | *** join/#maemo-ssu kolp (~quassel@212.255.230.192) |
| 10:36.12 | *** join/#maemo-ssu lizardo (lizardo@nat/indt/x-qvureewfqwsdqiru) |
| 10:37.36 | *** join/#maemo-ssu Wikiwide (~chatzilla@101.164.32.121) |
| 12:08.43 | *** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 12:11.20 | *** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 14:43.16 | *** join/#maemo-ssu infobot (~infobot@rikers.org) |
| 14:43.16 | *** topic/#maemo-ssu is Maemo Community Seamless Software Update "CSSU" channel, http://wiki.maemo.org/Community_SSU | Known bugs: http://j.mp/communityssu-bugs | Channel logs: http://mg.pov.lt/maemo-ssu-irclog/ | Sources: http://gitorious.org/community-ssu/ | Latest version: Testing(2013-10-27): 21.2011.38-1Tmaemo8.3; Stable(2013-06-18): 21.2011.38-1Smaemo6.1 |
| 14:43.18 | *** mode/#maemo-ssu [+v infobot] by ChanServ |
| 15:47.41 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
| 15:56.05 | *** join/#maemo-ssu psycho_oreos (~no@unaffiliated/tuxsavvy) |
| 15:58.40 | *** join/#maemo-ssu NIN101 (~NIN@p5DD29DD0.dip0.t-ipconnect.de) |
| 16:03.48 | *** join/#maemo-ssu dos11 (~dos@unaffiliated/dos1) |
| 18:10.07 | *** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 18:29.34 | freemangordon | Pali: https://maemo.gitorious.org/hildon/glib/commits/7b40ed8a77f69e1e2b1ec182b2ed559732eacc57 |
| 18:31.33 | freemangordon | Pali: what is the sane way to have that in cssu, to clone it, or to create a repo and pull/push? |
| 18:31.51 | freemangordon | merlin1991: ^^^ |
| 18:32.28 | Pali | create new repo and pull/push |
| 18:32.36 | freemangordon | ok |
| 18:33.30 | merlin1991 | are there glib patches that didn't make it into maemo? |
| 18:34.00 | freemangordon | well, stock is 2.20.3-1maemo5, in that repo there is 2.24.1 |
| 18:34.34 | freemangordon | merlin1991: what do you think? |
| 18:35.30 | freemangordon | 2.20 is from maybe 2008 |
| 18:40.11 | *** join/#maemo-ssu hbib (~wurmel@pD9E0F50A.dip0.t-ipconnect.de) |
| 18:41.07 | freemangordon | merlin1991: shall I create a repo and pull that in CSSU? |
| 18:41.14 | merlin1991 | sure |
| 18:41.22 | freemangordon | ok |
| 18:49.43 | freemangordon | done |
| 18:53.35 | freemangordon | merlin1991: BTW I think it is about time for a new big cssu update, we have a whole bunch of new packages ready for -testing |
| 18:54.06 | merlin1991 | yep it s |
| 18:54.25 | freemangordon | I know you're hort on time, but still :) |
| 18:54.30 | freemangordon | *short |
| 19:00.03 | anYc | also votes for new packages |
| 19:02.35 | freemangordon | glib builds fine, going to test it |
| 19:17.10 | *** join/#maemo-ssu freemangordon_ (~freemango@46.249.74.23) |
| 19:27.51 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 20:54.20 | *** join/#maemo-ssu NIN101 (~NIN@p5DD29DD0.dip0.t-ipconnect.de) |
| 21:00.40 | Raimu | Hehe, had the strangest yellow banner message from the CSSU's alarm-ui |
| 21:01.03 | Raimu | "Time left until alarm 9:60" |
| 21:01.40 | Raimu | I think it was because the time struck 23:00 right at the same time the application was deciding how to phrase the remaining time." |
| 21:17.55 | sixwheeledbeast | eh 9:60? |
| 21:52.58 | *** join/#maemo-ssu zumbi (zumbi@pasanda.collabora.co.uk) |
| 22:37.55 | Raimu | Yeah, it was 10 hours to go but I guess the hour changed at a funny point. |
| 22:44.40 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
| 22:45.27 | sixwheeledbeast | weird |
| 22:54.25 | *** join/#maemo-ssu KenYoung (~rtm@pool-108-20-253-215.bstnma.east.verizon.net) |
| 23:13.37 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-83-158.residential.rdsnet.ro) |
| 23:16.47 | DocScrutinizer05 | hihi |
| 23:18.35 | DocScrutinizer05 | this happens when coder doesn't obey one of golden rules: always call timing/metering functions only once, in an atomic way, then parse result and store to local vars |
| 23:24.17 | DocScrutinizer05 | if you however do crimes like printf("time: %2d:%2d", ftime() / 3600, ftime() - (ftime() / 3600)) [or similar] then you get results like the one sixwheeledbeast reported above |
| 23:25.30 | KenYoung | That's *really* bad code. |
| 23:25.55 | DocScrutinizer05 | s@ftime() - (ftime() / 3600)@(ftime % 60)/60 |
| 23:26.33 | DocScrutinizer05 | KenYoung: it's incorrect, but even when it was correct it still would be pretty BAD |
| 23:27.22 | DocScrutinizer05 | ftime() returns seconds,milliseconds since epoch, so the code above is garbage, but I just tried do illustrate something |
| 23:29.03 | *** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu) |
| 23:29.29 | DocScrutinizer05 | actually it *returns* always 0 |
| 23:29.57 | *** join/#maemo-ssu okias (~okias@berger.cust.centro-net.cz) |
| 23:32.01 | DocScrutinizer05 | the point however is: you NEVER call a readout function of a dynamic value multiple times. You always call it *once* and store the returned value to a local var |
| 23:32.11 | *** join/#maemo-ssu okias (~okias@berger.cust.centro-net.cz) |
| 23:32.55 | DocScrutinizer05 | obviously the coder of the app that created that notifier sixwheeledbeast seen didn't know that |
| 23:35.39 | DocScrutinizer05 | it could even get worse when the app hits a microsecond earlier then it may display 10:60 instead 10:00, a bit later and it displays 9:00 instead 10:00 |
| 23:36.50 | DocScrutinizer05 | on driver level when you can't do atomic reads (e.g. on cmos clock) you do two reads of all registers and compare. If they differ you read a third time, and so on |
| 23:50.10 | *** join/#maemo-ssu obiwlan (~obiwlan@p4FD2674E.dip0.t-ipconnect.de) |
| 23:59.26 | *** join/#maemo-ssu amizraa (~amizraa@gateway/tor-sasl/amizraa) |